This record as markdown: /tools/io-github-kivanccakmak-yaver/proxy-remove.md
What proxy_remove does on Yaver
AI agents call proxy_remove to permanently remove resources in Yaver, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
domain | string | Yes | Domain to remove |
Parameters from the server's own tool schema.
Why proxy_remove is rated Critical
Removing a reverse proxy route is a destructive action that cannot be trivially undone. It terminates network routing, breaks active connections, and disrupts service availability. While not as catastrophic as deleting application data, it irreversibly modifies infrastructure configuration and affects downstream systems.
From the tool's definition Tool name is 'proxy_remove' with description 'Remove a reverse proxy route' — the verb 'Remove' indicates irreversible deletion of a routing configuration.
Attacks that exploit this kind of access
The rule that runs proxy_remove safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For proxy_remove, this is the rule to start with:
proxy_remove 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 Yaver, apply this rule, and every proxy_remove call is checked against it from then on.
Questions about proxy_remove
Remove a reverse proxy route. It is categorised as a Destructive tool in the Yaver MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
proxy_remove accepts 1 parameter: domain. Required: domain. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for proxy_remove: 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 Yaver. Nothing to install.
proxy_remove 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 proxy_remove 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_remove. 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_remove is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
Across the catalogue