This record as markdown: /tools/7gugu-whistle-mcp/createrule.md
What createRule does on Whistle
AI agents use createRule 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 createRule is rated Medium
This tool creates new proxy rules, which is a write operation that modifies the proxy's behavior and network traffic interception. While reversible (rules can be deleted via deleteRule), it has high severity because misconfigured rules could intercept, redirect, or manipulate network traffic in harmful ways.
From the tool's definition Tool named 'createRule' with description '创建新规则' (create new rule). The server description indicates this tool is part of a Whistle proxy management system that 'enables AI assistants to directly operate and control local Whistle proxy servers' and 'manage…
Attacks that exploit this kind of access
The rule that runs createRule 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 createRule, this is the rule to start with:
createRule 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 createRule call is checked against it from then on.
Questions about createRule
创建新规则. 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 createRule: 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.
createRule 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 createRule 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 createRule. 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.
createRule 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