This record as markdown: /tools/7gugu-whistle-mcp/renamevaluegroup.md
What renameValueGroup does on Whistle
AI agents use renameValueGroup to create or update resources in Whistle, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Whistle environment.
Why renameValueGroup is rated Medium
This tool modifies metadata (group names) within the Whistle proxy system but does not delete data or execute arbitrary code. Renaming is a reversible Write operation. Severity is medium because renaming groups could disrupt proxy rule logic if done incorrectly, affecting network traffic handling, but the impact is typically recoverable by renaming back or updating references.
From the tool's definition Tool name 'renameValueGroup' and description '重命名值分组' (rename value group) indicates modification of existing data structure. The sibling tools show this is part of a proxy management system where groups organize values used in proxy rules.
Attacks that exploit this kind of access
The rule that runs renameValueGroup 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 renameValueGroup, this is the rule to start with:
renameValueGroup stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Whistle, apply this rule, and every renameValueGroup call is checked against it from then on.
Questions about renameValueGroup
重命名值分组. It is categorised as a Write tool in the Whistle MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Whistle MCP server in PolicyLayer and add a rule for renameValueGroup: 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.
renameValueGroup is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the renameValueGroup 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 renameValueGroup. 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.
renameValueGroup 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.
This server
Across the catalogue