This record as markdown: /tools/7gugu-whistle-mcp/disablerule.md
What disableRule does on Whistle
AI agents use disableRule 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 disableRule is rated Medium
Disabling a rule modifies existing configuration state but is reversible (the rule can be re-enabled). This falls under Write rather than Destructive since it does not delete or permanently remove data. The medium severity reflects that disabling rules could disrupt network traffic filtering if misconfigured by an agent, but the change is easily undoable.
From the tool's definition Tool name 'disableRule' and description '禁用规则' (disable rule) indicates modifying the state of an existing rule by disabling it. This is a reversible state change operation, similar to toggling a configuration.
Attacks that exploit this kind of access
The rule that runs disableRule 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 disableRule, this is the rule to start with:
disableRule 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 disableRule call is checked against it from then on.
Questions about disableRule
禁用规则. 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 disableRule: 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.
disableRule 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 disableRule 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 disableRule. 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.
disableRule 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