This record as markdown: /tools/7gugu-whistle-mcp/deletevalue.md
What deleteValue does on Whistle
AI agents call deleteValue 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 deleteValue is rated Critical
This tool permanently removes a value from the proxy management system without the ability to undo the operation. Deletion is an irreversible action that fits the Destructive category. While the impact is scoped to proxy configuration values rather than system-wide data, the loss of configuration could disrupt proxy rules and network interception logic, warranting high severity.
From the tool's definition Tool name 'deleteValue' and description '删除值' (Chinese: 'delete value') indicate irreversible deletion of data stored in the Whistle proxy configuration system.
Attacks that exploit this kind of access
The rule that runs deleteValue 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 deleteValue, this is the rule to start with:
deleteValue 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 deleteValue call is checked against it from then on.
Questions about deleteValue
删除值. 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 deleteValue: 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.
deleteValue 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 deleteValue 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 deleteValue. 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.
deleteValue 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