switch_organization
Switch the active organization context. Affects all subsequent API calls.
This record as markdown: /tools/app-businys-mcp-server/switch-organization.md
What switch_organization does on Businys
AI agents invoke switch_organization to trigger actions in Businys. 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_organization is rated High
This tool changes the active organizational context that governs all subsequent API calls. It doesn't merely read or write data in isolation — it triggers a persistent state change that affects every following operation in the session.
From the tool's definition Switch the active organization context. Affects all subsequent API calls.
Attacks that exploit this kind of access
The rule that runs switch_organization safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Businys, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For switch_organization, this is the rule to start with:
switch_organization 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 Businys, apply this rule, and every switch_organization call is checked against it from then on.
Questions about switch_organization
Switch the active organization context. Affects all subsequent API calls. It is categorised as a Execute tool in the Businys MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Businys MCP server in PolicyLayer and add a rule for switch_organization: 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 Businys. Nothing to install.
switch_organization 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_organization 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_organization. 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_organization is provided by the Businys MCP server (@businys/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Businys, and thousands of servers like it.
Across the catalogue