switch_tenant_id · Pointsyeah MCP: Risk & Policy

WHAT IT DOES

What switch_tenant_id does on Pointsyeah

AI agents invoke switch_tenant_id to trigger actions in Pointsyeah. 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 switch_tenant_id needs a policy

This tool changes the execution context for all subsequent API requests by switching the active tenant ID. It doesn't merely read or write data — it alters the operational environment/session state, affecting what data and operations are accessible. Misuse by an AI agent could cause all subsequent actions to target the wrong tenant, potentially leaking or corrupting data across tenant boundaries.

From the tool's definition Switch the active tenant ID used for all subsequent API requests. This is an admin tool for multi-tenant scenarios.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

switch_tenant_id Rate-limited

switch_tenant_id 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": {
    "switch_tenant_id": {
      "limits": [
        {
          "counter": "switch_tenant_id_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 Pointsyeah, so you can run agents against it safely.

FAQ

Questions about switch_tenant_id

What does the switch_tenant_id tool do? +

Switch the active tenant ID used for all subsequent API requests. This is an admin tool for multi-tenant scenarios. Pass an empty string to clear the tenant ID. It is categorised as a Execute tool in the Pointsyeah MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on switch_tenant_id? +

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

What risk level is switch_tenant_id? +

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

Can I rate-limit switch_tenant_id? +

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

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

switch_tenant_id is provided by the Pointsyeah MCP server (slack-workspace-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.