Check which APIs are available and current rate limit status.
AI agents call api_status to retrieve information from Github Insight without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves operational metadata about API availability and rate limits. It has no capability to modify data, execute code, delete resources, or trigger external operations. It is a simple diagnostic/monitoring read operation, making it low severity even if misused (worst case: an agent learns rate limit constraints and adapts accordingly).
From the tool's definition Tool is named 'api_status' and performs a status check operation. The description states it checks 'which APIs are available and current rate limit status' — purely informational queries with no mutations or side effects.
Attacks that exploit this kind of access
Check which APIs are available and current rate limit status. It is categorised as a Read tool in the Github Insight MCP Server, which means it retrieves data without modifying state.
Register the Github Insight MCP server in PolicyLayer and add a rule for api_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 Github Insight. Nothing to install.
api_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 api_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 api_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.
api_status is provided by the Github Insight MCP server (wjddusrb03/github-insight-mcp). 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 →