This record as markdown: /tools/7gugu-whistle-mcp/getinterceptinfo.md
What getInterceptInfo does on Whistle
AI agents call getInterceptInfo to retrieve information from Whistle without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why getInterceptInfo is rated Low
This tool retrieves network intercept data from the Whistle proxy server. While it only reads data without modifying or deleting it (classifying as 'Read'), the severity is elevated to 'medium' because intercepted request/response data can include sensitive information such as authentication tokens, personal data, API keys, and credentials.
From the tool's definition Tool name 'getInterceptInfo' and description indicating it retrieves/queries intercept information (requests/responses in base64 encoding) with no modification capability mentioned
Attacks that exploit this kind of access
The rule that runs getInterceptInfo 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 getInterceptInfo, this is the rule to start with:
getInterceptInfo is read-only, so it stays allowed. 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 getInterceptInfo call is checked against it from then on.
Questions about getInterceptInfo
获取URL的拦截信息(请求/响应皆以base64编码). It is categorised as a Read tool in the Whistle MCP Server, which means it retrieves data without modifying state.
Register the Whistle MCP server in PolicyLayer and add a rule for getInterceptInfo: 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.
getInterceptInfo is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the getInterceptInfo 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 getInterceptInfo. 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.
getInterceptInfo 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