Switch the active tenant for this MCP session.
AI agents use switch_tenant to create or update resources in BotUyo MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your BotUyo MCP Server environment.
Switching the active tenant modifies session state and redirects all subsequent tool operations to a different tenant context. While not permanently destructive or executing arbitrary code, this is a reversible Write operation with high blast radius: an AI agent switching to the wrong tenant could inadvertently perform intended operations (creates, updates, deletes via sibling tools) against the wrong organization's…
From the tool's definition Tool name is 'switch_tenant' and description states it switches 'the active tenant for this MCP session', indicating a state-modifying operation that affects which tenant context subsequent operations execute within.
Attacks that exploit this kind of access
Switch the active tenant for this MCP session. It is categorised as a Write tool in the BotUyo MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the BotUyo 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 BotUyo MCP Server. Nothing to install.
switch_tenant is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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 BotUyo MCP Server MCP server (marcoar1/botuyo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →