This record as markdown: /tools/7gugu-whistle-mcp/deletevaluegroup.md
What deleteValueGroup does on Whistle
AI agents call deleteValueGroup 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 deleteValueGroup is rated Critical
This tool permanently removes a values group without the ability to undo the operation. While not financial data, the deletion of proxy configuration groups could disrupt network monitoring and management workflows. Classified as Destructive rather than Write because the action is irreversible; users cannot recover deleted groups without manual reconfiguration.
From the tool's definition Tool name 'deleteValueGroup' combined with description '删除值分组' (Chinese: 'delete values group') indicates irreversible deletion of a grouped collection of values in the Whistle proxy configuration.
Attacks that exploit this kind of access
The rule that runs deleteValueGroup 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 deleteValueGroup, this is the rule to start with:
deleteValueGroup 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 deleteValueGroup call is checked against it from then on.
Questions about deleteValueGroup
删除值分组. 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 deleteValueGroup: 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.
deleteValueGroup 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 deleteValueGroup 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 deleteValueGroup. 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.
deleteValueGroup 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