Get detailed status of a specific interceptor, including all active targets and their details.
AI agents call interceptor_status to retrieve information from Proxy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves status information about active interceptors and targets without modifying them. While the broader proxy server has dangerous capabilities (traffic modification, mocking), this tool is a simple read-only query.
From the tool's definition Tool description states 'Get detailed status' which is a retrieval operation with no modification capability.
Documented attack patterns abuse exactly the kind of access interceptor_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Proxy, and nothing reaches the server without passing your rules. This is the rule we recommend for interceptor_status:
{
"version": "1",
"default": "deny",
"tools": {
"interceptor_status": {}
}
}interceptor_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get detailed status of a specific interceptor, including all active targets and their details. It is categorised as a Read tool in the Proxy MCP Server, which means it retrieves data without modifying state.
Register the Proxy MCP server in PolicyLayer and add a rule for interceptor_status: 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 Proxy. Nothing to install.
interceptor_status 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 interceptor_status 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 interceptor_status. 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.
interceptor_status is provided by the Proxy MCP server (yfe404/proxy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Proxy, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
89 Proxy tools catalogued and risk-classified — across an index of 43,000+ MCP servers.