This record as markdown: /tools/7gugu-whistle-mcp/togglehttp2.md
What toggleHttp2 does on Whistle
AI agents use toggleHttp2 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 toggleHttp2 is rated Medium
This tool modifies proxy server configuration by toggling HTTP/2 support on/off. This is a reversible Write operation—the setting can be toggled back—affecting how the proxy handles network protocols. The impact is medium severity because misconfiguration could disrupt network traffic or bypass security controls, but the change is not destructive and can be readily undone.
From the tool's definition Tool name 'toggleHttp2' with description '启用或禁用HTTP/2' (Enable or disable HTTP/2) indicates a configuration modification that toggles a protocol setting on the Whistle proxy server.
Attacks that exploit this kind of access
The rule that runs toggleHttp2 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 toggleHttp2, this is the rule to start with:
toggleHttp2 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 toggleHttp2 call is checked against it from then on.
Questions about toggleHttp2
启用或禁用HTTP/2. 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 toggleHttp2: 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.
toggleHttp2 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 toggleHttp2 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 toggleHttp2. 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.
toggleHttp2 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