Switch to a different Certificate Authority
AI agents invoke ssl_switch_ca to trigger actions in Web Proxy 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 the Certificate Authority on an HTTPS proxy is an operational action that affects how SSL/TLS traffic is intercepted and decrypted. It doesn't merely read data, nor does it irreversibly delete anything, but it triggers an external configuration change with significant security implications — altering which CA signs intercepted certificates could break TLS for all proxied clients or enable MitM attacks if…
From the tool's definition 'Switch to a different Certificate Authority' — changes the active CA used for SSL/TLS interception
Attacks that exploit this kind of access
Switch to a different Certificate Authority. It is categorised as a Execute tool in the Web Proxy MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Web Proxy MCP Server MCP server in PolicyLayer and add a rule for ssl_switch_ca: 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 Web Proxy MCP Server. Nothing to install.
ssl_switch_ca 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 ssl_switch_ca 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 ssl_switch_ca. 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.
ssl_switch_ca is provided by the Web Proxy MCP Server MCP server (mako10k/mcp-web-proxy). 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 →