replayRequest
在whistle中重放捕获的请求(本接口请求后不会直接返回结果, 需要使用getInterceptInfo接口获取结果)
This record as markdown: /tools/7gugu-whistle-mcp/replayrequest.md
What replayRequest does on Whistle
AI agents invoke replayRequest to trigger actions in Whistle. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why replayRequest is rated High
This tool replays previously captured network requests through the Whistle proxy, which constitutes executing an external operation (re-sending HTTP requests). It doesn't just read data or write local state — it actively triggers outbound network requests. The description also notes that results must be retrieved separately via getInterceptInfo, indicating an async external execution pattern.
From the tool's definition 重放捕获的请求 (replay captured requests) — triggers an external HTTP request operation
Attacks that exploit this kind of access
The rule that runs replayRequest 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 replayRequest, this is the rule to start with:
replayRequest stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 replayRequest call is checked against it from then on.
Questions about replayRequest
在whistle中重放捕获的请求(本接口请求后不会直接返回结果, 需要使用getInterceptInfo接口获取结果). It is categorised as a Execute tool in the Whistle MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Whistle MCP server in PolicyLayer and add a rule for replayRequest: 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.
replayRequest is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the replayRequest 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 replayRequest. 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.
replayRequest 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.
Across the catalogue