For the complete documentation index, see llms.txt. Markdown versions of all docs pages are available by appending .md to any docs URL.

Inspect, mutate, or reject MCP requests and responses with in-process CEL expressions or a remote ExtMCP policy server.

Use guardrail processors (mcpGuardrails) to inspect, rewrite, or reject Model Context Protocol (MCP) requests and responses. Write processors as Common Expression Language (CEL) expressions that run inside agentgateway, or use an external gRPC server that implements ExtMCP.

Guardrail processors are one of three ways to filter MCP traffic. To compare them with target conditions and MCP authorization, see About MCP guardrails.

About guardrail processors

Agentgateway supports external authorization and external processing (ExtProc) for HTTP traffic. These integrations require the external server to assemble the HTTP body, parse JSON-RPC, and handle MCP framing.

Guardrail processors receive the MCP method name, target, and request parameters or response result directly. They can evaluate access to tools, prompts, and resources without parsing raw HTTP.

Common use cases include the following:

• Reject tools/call requests based on the tool name, its arguments, or the caller’s identity.
• Mask sensitive data in tool arguments before they reach the MCP server, or in results before they reach the client.
• Rewrite tools/list responses, such as to annotate tool descriptions.
• Centralize MCP policy logic in an external service that you already operate.

Processor types

Configure guardrails as an ordered list of processors. Each processor handles selected MCP methods and uses one of these types:

You can combine both types in the same guardrails policy. For example, reject disallowed calls with CEL before a remote processor runs more expensive checks.

How it works

For each configured MCP method, processors run in the request phase, response phase, or both.

Rejections return a JSON-RPC error for methods other than tools/call. For tools/call, denials return a tool result with isError: true, except for internal errors. See Error codes for details.

The following diagram shows a remote processor. A CEL expression processor follows the same flow, but agentgateway evaluates the expression in-process instead of calling an external server.

    sequenceDiagram
    autonumber
    participant Client as MCP client
    participant AGW as agentgateway
    participant Ext as ExtMCP server
    participant MCP as MCP backend
    Client->>AGW: tools/call (JSON-RPC)
    AGW->>Ext: CheckRequest (method, tool, params, headers)
    alt Request denied
        Ext-->>AGW: AuthorizationError
        AGW-->>Client: Denied response
    else Request passed or mutated
        Ext-->>AGW: Pass request or return mutated params
        AGW->>MCP: Forward request
        MCP-->>AGW: Result
        AGW->>Ext: CheckResponse (result)
        alt Response denied
            Ext-->>AGW: AuthorizationError
            AGW-->>Client: Denied response
        else Response passed or mutated
            Ext-->>AGW: Pass or return mutated response
            AGW-->>Client: Result
        end
    end
  

Each processor returns one of three outcomes for each call:

• Pass: Allow the request or response unchanged.
• Mutate: Replace the JSON-RPC params (request phase) or result (response phase) before agentgateway forwards it.
• Deny: Return an error to the client in either phase.

Request mutation trust boundary

Treat processors that can change JSON-RPC params as trusted components. They can change the request sent upstream, but cannot change the selected backend.

For tools/call, prompts/get, and resources/read, agentgateway selects the backend and resolves the requested name or URI before processors run. MCP authorization checks that original backend and resolved identifier after the processors allow the request. Changing an identifier does not cause agentgateway to resolve it again or update the authorization context.

To authorize the changed identifier or parameters, add a processor that checks them after the last mutating processor. Alternatively, enforce that check in the final mutating processor.

Configuration

This policy first rejects calls to delete_records with CEL. It then sends tool calls and tool listings to a remote ExtMCP server.

mcpGuardrails:
  processors:
  - kind: expression
    condition: mcp.params.name == "delete_records"
    reject: "delete_records is not available through this gateway"
    methods:
      tools/call: request
  - kind: remote
    host: "localhost:9001"
    failureMode: failClosed
    methods:
      tools/call: request
      tools/list: response

Each processor uses a methods map to select MCP methods and phases. Other settings depend on its type.

CEL expression processors

A CEL expression processor evaluates an optional condition. Set exactly one action: reject or transform.

Expression processors can read the usual MCP policy variables, such as request, jwt, mcp.methodName, and mcp.tool. They also expose these payload variables:

Use has() to check optional fields before reading them. A missing field can cause an evaluation error.

Processors run in order, and each processor sees the changes from earlier processors. To make a rejection rule see the original request, list it before any processor that masks the same fields.

Use regexReplace to replace the first regular expression match, or regexReplaceAll to replace every non-overlapping match. Both support capture groups in replacements, such as $1. For the full list of functions, see the CEL reference.

Expression processors fail closed and do not support failureMode. If an expression fails to evaluate, or if a transform returns a body that is not a valid MCP message, agentgateway rejects the call with an internal error.

Remote processors

A remote processor calls an external gRPC server that implements the ExtMCP protocol. ExtMCP follows the model of Envoy’s ext_authz filter. The server receives the MCP method name, target, request parameters or response result, and selected request headers.

• The ExtMCP server: The remote reference, such as host points to the gRPC server that enforces the processor.
• The failure mode: The failureMode setting controls what happens when the server is unreachable or returns an error. See Failure modes.

Methods

The methods map keys are the JSON-RPC method names from the MCP specification, such as tools/call, tools/list, prompts/get, and resources/read. Each key maps to the phase in which agentgateway runs the processor for that method.

Method keys can be exact (tools/call), a prefix wildcard (tools/*), a suffix wildcard (*/list), or * for all methods. The most specific match wins. Methods that match no key, including unknown methods, bypass the processor.

Phases

Set a phase for each method to control when its processor runs.

Failure modes

The failureMode setting of a remote processor controls what happens when the server is unreachable or returns an error.

Ordering and multiplexing

Keep the following behaviors in mind when you design a policy:

• MCP authentication runs before request-phase processors. Agentgateway does not repeat authentication after request mutation.
• Processors run in the order listed. The first processor to deny a request short-circuits the chain.
• Request-phase processors run before MCP authorization. If a processor rejects a call, MCP authorization does not run for that call.
• Request-phase processors receive tool and prompt names without the target-name prefix. Agentgateway passes the target name separately.
• For fanout methods such as tools/list, the request phase runs once before agentgateway contacts any target. The response phase runs once on the merged result, after MCP authorization removes denied items. Multiplexed names include the target-name prefix, such as everything_echo.

Error codes

When a processor denies a call, agentgateway returns a JSON-RPC error to the client. A CEL expression processor that rejects a call returns the -32001 code, the same as a remote PERMISSION_DENIED. For a remote processor, the server’s authorization code maps to a JSON-RPC error code:

The error message comes from the CEL processor’s reject setting or the remote server’s reason field.

A remote server can also set mcp_error to a JSON value for the error’s data field. This payload does not change the code or message. Agentgateway ignores invalid JSON.

For tools/call, the table applies only to UNKNOWN and internal failures. Examples include a CEL evaluation error or an unreachable remote server configured to fail closed.

Other tools/call denials return HTTP 200 with a tool result containing isError: true and the rejection message. This result does not include mcp_error. For all other MCP methods, the table applies to every code.