This record as markdown: /tools/7gugu-whistle-mcp/deleterule.md
What deleteRule does on Whistle
AI agents call deleteRule to permanently remove resources in Whistle, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why deleteRule is rated Critical
Deleting rules from a Whistle proxy server removes configurations that may be critical to network request handling, filtering, or monitoring. This action is irreversible and could disrupt network traffic management if misused by an AI agent. The blast radius includes potential loss of important proxy configurations and inability to restore them without manual intervention.
From the tool's definition Tool name 'deleteRule' and description '删除规则' (Chinese: 'delete rule') indicate irreversible deletion of proxy rules. Combined with sibling tools like deleteGroup, deleteValue, deleteValueGroup, this is clearly a destructive operation that cannot be undone.
Attacks that exploit this kind of access
The rule that runs deleteRule safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Whistle, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For deleteRule, this is the rule to start with:
deleteRule 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 Whistle, apply this rule, and every deleteRule call is checked against it from then on.
Questions about deleteRule
删除规则. It is categorised as a Destructive tool in the Whistle MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Whistle MCP server in PolicyLayer and add a rule for deleteRule: 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 Whistle. Nothing to install.
deleteRule 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 deleteRule 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 deleteRule. 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.
deleteRule is provided by the Whistle MCP server (7gugu/whistle-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Whistle, and thousands of servers like it.
Across the catalogue