passgage_switch_to_user_mode · Passgage MCP Server MCP

WHAT IT DOES

What passgage_switch_to_user_mode does on Passgage MCP Server

AI agents invoke passgage_switch_to_user_mode to trigger actions in Passgage MCP Server. 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 passgage_switch_to_user_mode needs a policy

This tool changes the authentication context/mode of the session, switching to a different JWT token. It triggers an operational state change in how the system authenticates subsequent requests. This is not a simple read, nor does it create/modify data records — it executes an authentication mode switch that affects all downstream API calls.

From the tool's definition Switch to user JWT authentication mode (requires previous user login)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

passgage_switch_to_user_mode Rate-limited

passgage_switch_to_user_mode 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": {
    "passgage_switch_to_user_mode": {
      "limits": [
        {
          "counter": "passgage_switch_to_user_mode_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 Passgage MCP Server, so you can run agents against it safely.

FAQ

Questions about passgage_switch_to_user_mode

What does the passgage_switch_to_user_mode tool do? +

Switch to user JWT authentication mode (requires previous user login). It is categorised as a Execute tool in the Passgage MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on passgage_switch_to_user_mode? +

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

What risk level is passgage_switch_to_user_mode? +

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

Can I rate-limit passgage_switch_to_user_mode? +

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

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

passgage_switch_to_user_mode is provided by the Passgage MCP Server MCP server (passgage/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.