Check the status of an async chain execution (returned from call_api with async: true).
AI agents call get_chain_status to retrieve information from APIClaw without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries the status of an already-executed async chain. It has no side effects, cannot modify or delete data, and does not trigger new operations. It is purely informational, fitting the 'Read' category. The blast radius of misuse is minimal—an agent might check status of chains it shouldn't have visibility into, but this poses only an information disclosure risk at low severity.
From the tool's definition Tool name 'get_chain_status' and description 'Check the status of an async chain execution' indicates query/retrieval of execution status without modifying, deleting, or executing operations.
Documented attack patterns abuse exactly the kind of access get_chain_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and APIClaw, and nothing reaches the server without passing your rules. This is the rule we recommend for get_chain_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_chain_status": {}
}
}get_chain_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.
Check the status of an async chain execution (returned from call_api with async: true). It is categorised as a Read tool in the APIClaw MCP Server, which means it retrieves data without modifying state.
Register the APIClaw MCP server in PolicyLayer and add a rule for get_chain_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 APIClaw. Nothing to install.
get_chain_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 get_chain_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 get_chain_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.
get_chain_status is provided by the APIClaw MCP server (nordsym/apiclaw). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from APIClaw, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
24 APIClaw tools catalogued and risk-classified — across an index of 43,000+ MCP servers.