This record as markdown: /tools/7gugu-whistle-mcp/updaterule.md
What updateRule does on Whistle
AI agents use updateRule 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 updateRule is rated Medium
The tool modifies proxy rules which control network traffic interception and manipulation. While reversible (Write category), the severity is high because misconfigured proxy rules could redirect, intercept, or manipulate network traffic for all applications using the proxy, potentially affecting security, privacy, and application functionality.
From the tool's definition Tool name 'updateRule' and description '更新规则内容' (update rule content) indicate modification of existing proxy rules. This is reversible modification of proxy configuration data.
Attacks that exploit this kind of access
The rule that runs updateRule 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 updateRule, this is the rule to start with:
updateRule 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 updateRule call is checked against it from then on.
Questions about updateRule
更新规则内容. 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 updateRule: 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.
updateRule 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 updateRule 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 updateRule. 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.
updateRule 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