delete-proxy
A destructive tool on the AdsPower LocalAPI MCP server.
This record as markdown: /tools/adspower-adspower-browser/delete-proxy.md
What delete-proxy does on AdsPower LocalAPI MCP Server
AI agents call delete-proxy to permanently remove resources in AdsPower LocalAPI MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete-proxy is rated Critical
The tool performs an irreversible deletion action (delete-proxy) that cannot be undone. While the description is empty, the naming convention clearly indicates data destruction. This is classified as Destructive rather than Write because deletion operations are permanent.
From the tool's definition Tool name is 'delete-proxy' with no description provided. The 'delete-' prefix indicates irreversible deletion of proxy configuration data.
Attacks that exploit this kind of access
The rule that runs delete-proxy safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AdsPower LocalAPI MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete-proxy, this is the rule to start with:
delete-proxy is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect AdsPower LocalAPI MCP Server, apply this rule, and every delete-proxy call is checked against it from then on.
Questions about delete-proxy
delete-proxy is a destructive tool on the AdsPower LocalAPI MCP Server MCP server. It is categorised as a Destructive tool in the AdsPower LocalAPI MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AdsPower LocalAPI MCP Server MCP server in PolicyLayer and add a rule for delete-proxy: 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 AdsPower LocalAPI MCP Server. Nothing to install.
delete-proxy is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete-proxy 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 delete-proxy. 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.
delete-proxy is provided by the AdsPower LocalAPI MCP Server MCP server (adspower/adspower-browser). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AdsPower LocalAPI MCP Server, and thousands of servers like it.
Across the catalogue