Switches the active API project context to a previously registered project.
AI agents use switch-project to create or update resources in Swagger MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Swagger MCP Server environment.
The tool changes application state by switching which project is active. This is a reversible modification (can switch back to another project), so it does not qualify as Destructive. It does not read data (Execute category would apply if it triggered external operations, but switching context is an internal state change).
From the tool's definition Tool switches the 'active API project context' - this modifies internal state and affects which API documentation/project is currently in focus for subsequent tool operations.
Attacks that exploit this kind of access
Switches the active API project context to a previously registered project. It is categorised as a Write tool in the Swagger MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Swagger MCP Server MCP server in PolicyLayer and add a rule for switch-project: 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 Swagger MCP Server. Nothing to install.
switch-project 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-project 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-project. 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-project is provided by the Swagger MCP Server MCP server (nksmkj7/swagger-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 →