hippo_provider_switch
FORGIA #201. Switch the active LLM provider at runtime
This record as markdown: /tools/verimem/hippo-provider-switch.md
What hippo_provider_switch does on Verimem
AI agents invoke hippo_provider_switch to trigger actions in Verimem. 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 hippo_provider_switch is rated High
This tool changes the active LLM provider at runtime, which is an operational configuration change that affects how the entire system processes requests. It triggers an external operation (provider switch) whose effects depend on arguments (which provider to switch to).
From the tool's definition Switch the active LLM provider at runtime
Attacks that exploit this kind of access
The rule that runs hippo_provider_switch safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Verimem, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hippo_provider_switch, this is the rule to start with:
hippo_provider_switch 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 Verimem, apply this rule, and every hippo_provider_switch call is checked against it from then on.
Questions about hippo_provider_switch
FORGIA #201. Switch the active LLM provider at runtime. It is categorised as a Execute tool in the Verimem MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Verimem MCP server in PolicyLayer and add a rule for hippo_provider_switch: 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 Verimem. Nothing to install.
hippo_provider_switch 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 hippo_provider_switch 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 hippo_provider_switch. 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.
hippo_provider_switch is provided by the Verimem MCP server (aureliocpr-ctrl/verimem). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Verimem, and thousands of servers like it.
Across the catalogue