New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

renameGroup

重命名分组

SERVERWhistle SOURCE7gugu/whistle-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about renameGroup

What does the renameGroup tool do? +

重命名分组. 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.

How do I enforce a policy on renameGroup? +

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.

What risk level is renameGroup? +

renameGroup is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit renameGroup? +

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.

How do I block renameGroup completely? +

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.

What MCP server provides renameGroup? +

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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Whistle's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.