check_category
AI agents call check_category to retrieve information from API Status Check MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears designed to query or filter API status data by category (likely groupings like 'cloud services', 'payment processors', etc.). This is a passive information retrieval operation with no side effects, no code execution, and no financial impact. Misuse would be limited to information gathering; the blast radius is minimal.
From the tool's definition Tool is part of an API status monitoring server with sibling tools including 'check_status', 'check_url', and 'list_apis/list_categories'.
Attacks that exploit this kind of access
check_category. It is categorised as a Read tool in the API Status Check MCP Server MCP Server, which means it retrieves data without modifying state.
Register the API Status Check MCP Server MCP server in PolicyLayer and add a rule for check_category: 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 API Status Check MCP Server. Nothing to install.
check_category 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 check_category 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 check_category. 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.
check_category is provided by the API Status Check MCP Server MCP server (shibley/apistatuscheck-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →