AI agents call mcp_status to retrieve information from 1MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves status information about MCP servers, which is a read-only operation with no side effects. It does not create, modify, delete, execute code, or move money. The query returns existing state information only.
From the tool's definition Tool name 'mcp_status' and description 'Get MCP server status' indicate a retrieval operation that queries the current state of MCP servers without modifying, executing, or deleting anything.
Documented attack patterns abuse exactly the kind of access mcp_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and 1MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for mcp_status:
{
"version": "1",
"default": "deny",
"tools": {
"mcp_status": {}
}
}mcp_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 MCP server status. It is categorised as a Read tool in the 1MCP Server MCP Server, which means it retrieves data without modifying state.
Register the 1MCP Server MCP server in PolicyLayer and add a rule for mcp_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 1MCP Server. Nothing to install.
mcp_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 mcp_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 mcp_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.
mcp_status is provided by the 1MCP Server MCP server (1mcp-app/agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 17 1MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
17 1MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.