Skip to content

v1.4.4 - Stateful MCP Trajectory Enforcement

Choose a tag to compare

@sagarchhatrala sagarchhatrala released this 21 Jul 12:21

v1.4.4 - Stateful MCP Trajectory Enforcement

Agent Circuit Breaker v1.4.4 connects the v1.4.3 trajectory engine to the MCP proxy.

Highlights

  • Added circuit-breaker-mcp-proxy --trajectory for stateful checks across multiple MCP tools/call messages.
  • Added --trajectory-policy <path> for loading a JSON run contract.
  • Added MCPRunGuard for programmatic integrations.
  • MCP JSON-RPC block responses now include trajectory verdict and trajectory finding metadata when a run-level finding blocks a call.

Example

circuit-breaker-mcp-proxy --trajectory-policy ./agent-run-policy.json -- python -m your_mcp_server

With trajectory mode enabled, a tool call that reads .env followed by a later tool call that uploads data can be blocked even when either action alone would not match a built-in single-action block rule.

Compatibility

Default MCP proxy behavior remains stateless. Existing circuit-breaker-mcp-proxy deployments only get run-level checks when they opt in with --trajectory, --trajectory-policy, or the programmatic MCPRunGuard.

Verification

  • MCP stateless compatibility regression
  • MCP secret-read then egress sequence regression
  • MCP output-channel drift regression
  • full unit test suite