switch_context · Coord MCP: Risk & Policy

WHAT IT DOES

What switch_context does on CoordMCP

AI agents use switch_context to create or update resources in CoordMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CoordMCP environment.

WHY IT NEEDS A POLICY

Why switch_context needs a policy

An AI agent can call switch_context faster than any human can review — one bad instruction and it creates or modifies resources in CoordMCP by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

switch_context Rate-limited

switch_context stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "switch_context": {
      "limits": [
        {
          "counter": "switch_context_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about switch_context

What does the switch_context tool do? +

switch_context. It is categorised as a Write tool in the CoordMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on switch_context? +

Register the Coord MCP server in PolicyLayer and add a rule for switch_context: 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 CoordMCP. Nothing to install.

What risk level is switch_context? +

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

Can I rate-limit switch_context? +

Yes. Add a rate_limit block to the switch_context 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 switch_context completely? +

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

switch_context is provided by the Coord MCP server (siddiquesahabaj/coordmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

switch_context is one line of Coord's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →