Skip to main content
ClawQL
PluginOpt inclawql-api (PanguardProxyPlugin)

Plugins · Registry · Plugin model

Panguard MCP proxy

Hands-on walkthrough: Panguard MCP enforcement (Learn) — stdio wrap, in-process hooks, Helm mcpProxy, and JWT bridge env.

Plugin ID: panguard-mcp-proxy
Shape: hooks-only ProviderPlugin (does not register MCP tools)
Package: clawql-api — createPanguardProxyPlugin

The Panguard proxy plugin registers a blocking tool / pre-execute hook for policy enforcement when ClawQL runs behind an enterprise MCP proxy or with in-process ATR rules (#272). McpProxyPipeline fires hooks via fireHook (ATR never-loosen).

8.0+: enforcement providers are default-off. A bare install has no tool-scope enforcement until you opt in. Boot emits a SECURITY WARNING when none is active (silence with CLAWQL_ALLOW_NO_ENFORCEMENT=1 only if intentional).

What it does

  • Intercepts every MCP tool call before execution (blocking pre-execute)
  • Applies JWT ATR / policy decisions (allow, deny, scope checks)
  • Does not add tools to the MCP surface — it only gates existing ones

Enable / disable

EnvDefaultEffect
CLAWQL_PANGUARD_PROXY_PLUGIN=1offRegister the proxy plugin in composition
CLAWQL_PANGUARD_IN_PROCESS=1offActive in-process policy path (blocking hooks)
CLAWQL_ALLOW_NO_ENFORCEMENT=1offSilence boot warning when no enforcement is active

When to use

  • Kubernetes deployments with an intercepting MCP proxy
  • Defense-in-depth stacks documented in Defense in depth
  • Operators who need a single audit chokepoint before execute reaches upstream APIs

Learn more