Check which academic API sources are currently configured
AI agents call check_api_status to retrieve information from Q1 Crafter MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure information-retrieval tool that checks the operational status of API sources. It has no side effects, performs no modifications, executes no external operations beyond a simple status check, and poses minimal risk if misused by an AI agent. The action is read-only and informational.
From the tool's definition Tool name 'check_api_status' and description 'Check which academic API sources are currently configured' indicate a query operation that retrieves configuration status without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Check which academic API sources are currently configured. It is categorised as a Read tool in the Q1 Crafter MCP MCP Server, which means it retrieves data without modifying state.
Register the Q1 Crafter MCP server in PolicyLayer and add a rule for check_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 Q1 Crafter MCP. Nothing to install.
check_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 check_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 check_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.
check_api_status is provided by the Q1 Crafter MCP server (muslus/q1-crafter-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 →