switch_tenant
Switch the active tenant/environment at runtime. Changes which API endpoint, credentials, and tools are available. Use list_tenants to see available options.
This record as markdown: /tools/instantkom-mcp-server/switch-tenant.md
What switch_tenant does on instantKOM MCP Server
AI agents invoke switch_tenant to trigger actions in instantKOM 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 switch_tenant is rated High
This tool changes the active operational context at runtime, affecting which API endpoints, credentials, and tools are available. It doesn't merely read or write data — it reconfigures the execution environment, potentially redirecting all subsequent operations to a different tenant. Misuse could expose data from or cause actions against an unintended tenant/environment, making this a high-severity Execute action.
From the tool's definition Switch the active tenant/environment at runtime. Changes which API endpoint, credentials, and tools are available.
Attacks that exploit this kind of access
The rule that runs switch_tenant safely
PolicyLayer is an MCP gateway: it sits between your AI agents and instantKOM MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For switch_tenant, this is the rule to start with:
switch_tenant 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.
The button opens the PolicyLayer dashboard: create your workspace, connect instantKOM MCP Server, apply this rule, and every switch_tenant call is checked against it from then on.
Questions about switch_tenant
Switch the active tenant/environment at runtime. Changes which API endpoint, credentials, and tools are available. Use list_tenants to see available options. It is categorised as a Execute tool in the instantKOM MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the instantKOM MCP Server MCP server in PolicyLayer and add a rule for switch_tenant: 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 instantKOM MCP Server. Nothing to install.
switch_tenant is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the switch_tenant 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.
Set action: deny in the PolicyLayer policy for switch_tenant. 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.
switch_tenant is provided by the instantKOM MCP Server MCP server (instantkom/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on instantKOM MCP Server, and thousands of servers like it.
Across the catalogue