Check which APIs are configured and available.
AI agents call api_status to retrieve information from Content Research without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about API availability and configuration state. It is a pure read operation—no data is created, modified, deleted, or executed. The blast radius of misuse is minimal; an adversary learning which APIs are available poses no direct harm. Confidence is high because the name and description unambiguously describe a read-only status check.
From the tool's definition Tool name 'api_status' and description 'Check which APIs are configured and available' indicate it performs a status check/query operation with no side effects.
Attacks that exploit this kind of access
Check which APIs are configured and available. It is categorised as a Read tool in the Content Research MCP Server, which means it retrieves data without modifying state.
Register the Content Research 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 Content Research. 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 Content Research MCP server (wjddusrb03/content-research-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 →