Manually switch to the next available model tier
AI agents use switch_model to create or update resources in OpenAI Token Manager MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OpenAI Token Manager MCP environment.
The tool changes system state (active model selection) but does not delete data, execute arbitrary code, or move money. It is reversible—users can switch back to a previous tier. While it could have downstream effects on costs and API behavior, the direct action is configuration modification, placing it in the Write category.
From the tool's definition Tool description states it 'Manually switch to the next available model tier', which modifies the configuration or state of which model is being used. This is a reversible configuration change.
Attacks that exploit this kind of access
Manually switch to the next available model tier. It is categorised as a Write tool in the OpenAI Token Manager MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the OpenAI Token Manager MCP server in PolicyLayer and add a rule for switch_model: 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 OpenAI Token Manager MCP. Nothing to install.
switch_model 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_model 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_model. 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_model is provided by the OpenAI Token Manager MCP server (opaldecisionsciences/openai-token-manager-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 →