renameRule

重命名规则

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/renamerule.md

WHAT IT DOES

What renameRule does on Whistle

AI agents use renameRule 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.

RISK

Why renameRule is rated Medium

Renaming a rule is a reversible modification operation that changes metadata of an existing proxy rule without deleting data or executing external code. This fits the Write category.

From the tool's definition Tool name 'renameRule' combined with context of a proxy management system that modifies rule configurations. The description '重命名规则' (rename rule) indicates modification of existing data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs renameRule 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 renameRule, this is the rule to start with:

renameRule Rate-limited

renameRule 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "renameRule": {
      "limits": [
        {
          "counter": "renamerule_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Whistle, apply this rule, and every renameRule call is checked against it from then on.

FAQ

Questions about renameRule

What does the renameRule 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 renameRule? +

Register the Whistle MCP server in PolicyLayer and add a rule for renameRule: 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 renameRule? +

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

Can I rate-limit renameRule? +

Yes. Add a rate_limit block to the renameRule 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 renameRule completely? +

Set action: deny in the PolicyLayer policy for renameRule. 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 renameRule? +

renameRule 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.

KEEP EXPLORING

More on Whistle, and thousands of servers like it.

This server

All 34 Whistle tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →