route_to_pool · Session Buddy MCP: Risk & Policy

WHAT IT DOES

What route_to_pool does on Session Buddy

AI agents invoke route_to_pool to trigger actions in Session Buddy. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why route_to_pool needs a policy

This tool performs an operational routing action — directing a task to a pool using a strategy — which constitutes triggering an external operation whose effects depend on arguments. It is not a simple read (no data retrieval), nor clearly write/destructive/financial. The routing action executes logic that determines where work is dispatched, similar to a load-balancer or task scheduler operation.

From the tool's definition Route task to best available pool using specified strategy

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

route_to_pool Rate-limited

route_to_pool stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "route_to_pool": {
      "limits": [
        {
          "counter": "route_to_pool_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Session Buddy, so you can run agents against it safely.

FAQ

Questions about route_to_pool

What does the route_to_pool tool do? +

Route task to best available pool using specified strategy. It is categorised as a Execute tool in the Session Buddy MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on route_to_pool? +

Register the Session Buddy MCP server in PolicyLayer and add a rule for route_to_pool: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Session Buddy. Nothing to install.

What risk level is route_to_pool? +

route_to_pool is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit route_to_pool? +

Yes. Add a rate_limit block to the route_to_pool rule in your PolicyLayer 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 route_to_pool completely? +

Set action: deny in the PolicyLayer policy for route_to_pool. 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 route_to_pool? +

route_to_pool is provided by the Session Buddy MCP server (lesleslie/session-buddy). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.