Agent Static Deny plugin
The Agent Static Deny plugin blocks requests that match fixed rules on method, path, caller type, consumer type, or scope. Rules are checked in order, and the first matching rule blocks the request. A rule applies to every caller, not only agents, unless it sets a caller condition.
Where it runs
Configuration
The deny rules. The console labels this Deny rules. A rule matches when every condition it sets holds. A rule with no conditions is ignored.
The rule name, returned in the response.
The reason returned in the response. The default is denied: <name>, or request denied by agent-static-deny when the rule has no name.
HTTP methods, in any letter case.
Paths that must match exactly.
Path prefixes. Together with path_exact, the path must match one entry.
agent (or bot) and user (or human). Matches only callers with an agent identity.
Consumer types from the caller’s agent identity, in any letter case.
Matches a caller whose agent identity holds at least one of these scopes.
Paths are compared case-sensitively, after the route rewrites the path. If any entry in rules isn’t an object, every rule is ignored.
A blocked request gets 403 with {"error":"forbidden","reason":"...","rule":"..."}. On MCP routes, it gets HTTP 200 with JSON-RPC error -32002. The upstream isn’t called.

