Set the session
AI agents invoke wafle_users_switch_tenant to trigger actions in wafle 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.
Switching tenants changes the active session context, affecting which store/tenant all subsequent operations are performed against. This is an Execute-level action because it triggers an external state change (session manipulation) that can have wide-ranging downstream effects if misused — e.g., an agent could inadvertently operate on the wrong tenant's data.
From the tool's definition 'Set the session' — switches the active tenant/session context for the user
Attacks that exploit this kind of access
Set the session. It is categorised as a Execute tool in the wafle MCP server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the wafle MCP server MCP server in PolicyLayer and add a rule for wafle_users_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 wafle MCP server. Nothing to install.
wafle_users_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 wafle_users_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 wafle_users_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.
wafle_users_switch_tenant is provided by the wafle MCP server MCP server (the33warehouse-tech/wafle-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 →