This record as markdown: /tools/7gugu-whistle-mcp/renamegroup.md
What renameGroup does on Whistle
AI agents use renameGroup 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 renameGroup is rated Medium
Renaming a group is a data modification operation that can be undone (the group can be renamed back). It does not execute arbitrary code, delete irreversible data, or move financial resources. It falls under Write category. Severity is medium because misconfigured Whistle proxy rules could disrupt network monitoring/interception, but the rename itself only affects metadata structure and is easily recoverable.
From the tool's definition Tool name 'renameGroup' and description indicate modification of group naming in Whistle proxy management. This is a reversible write operation that changes metadata (group name) without deleting data or executing code.
Attacks that exploit this kind of access
The rule that runs renameGroup 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 renameGroup, this is the rule to start with:
renameGroup 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 renameGroup call is checked against it from then on.
Questions about renameGroup
重命名分组. 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 renameGroup: 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.
renameGroup 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 renameGroup 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 renameGroup. 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.
renameGroup 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