Stop the proxy server
AI agents invoke proxy_stop_server 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.
Stopping a proxy server is an Execute action because it triggers an external operation (server shutdown) whose effects depend on runtime state. While not permanently destructive, it causes immediate service interruption affecting all dependent traffic monitoring and analysis. This is more severe than Write (no data modification) but less severe than Destructive (service can be restarted).
From the tool's definition Tool name 'proxy_stop_server' and description 'Stop the proxy server' indicate execution of a server control operation that terminates an active service.
Attacks that exploit this kind of access
Stop the proxy server. 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 proxy_stop_server: 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.
proxy_stop_server 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 proxy_stop_server 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 proxy_stop_server. 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.
proxy_stop_server 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 →