Medium Risk

clawback_route

Route an LLM completion to the cheapest model that meets your quality bar. Requires routing to be active — call clawback with action=activate_routing first. Returns the full completion, the model used, and per-call savings. Recommended: set CLAWBACK_API_KEY env var instead of passing api_key inline.

Handles credentials or secrets (api_key)

Part of the Clawbackai MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

clawbackai-mcp Write Risk 3/5

AI agents use clawback_route to create or modify resources in Clawbackai. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call clawback_route repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Clawbackai.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

io-github-rckl88-clawbackai-mcp.yaml
tools:
  clawback_route:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Clawbackai policy for all 2 tools.

Tool Name clawback_route
Category Write
Risk Level Medium

Agents calling write-class tools like clawback_route have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the clawback_route tool do? +

Route an LLM completion to the cheapest model that meets your quality bar. Requires routing to be active — call clawback with action=activate_routing first. Returns the full completion, the model used, and per-call savings. Recommended: set CLAWBACK_API_KEY env var instead of passing api_key inline.. It is categorised as a Write tool in the Clawbackai MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on clawback_route? +

Add a rule in your Intercept YAML policy under the tools section for clawback_route. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Clawbackai MCP server.

What risk level is clawback_route? +

clawback_route is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit clawback_route? +

Yes. Add a rate_limit block to the clawback_route rule in your Intercept policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block clawback_route completely? +

Set action: deny in the Intercept policy for clawback_route. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides clawback_route? +

clawback_route is provided by the Clawbackai MCP server (clawbackai-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Clawbackai

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.