Check status, audit events, cost, and final result for a mission started via start_mission.
AI agents call mission_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.
mission_status performs read-only queries on mission data. It returns information about an existing mission's state, audit trail, expenses, and outcomes without creating, modifying, deleting, or triggering any new operations. This is a monitoring/inspection function with no blast radius.
From the tool's definition Tool retrieves mission status, audit events, cost, and final result. Keywords: 'check status', 'audit events', 'cost', 'final result' indicate data retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access mission_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 mission_status:
{
"version": "1",
"default": "deny",
"tools": {
"mission_status": {}
}
}mission_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 status, audit events, cost, and final result for a mission started via start_mission. 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 mission_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.
mission_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 mission_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 mission_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.
mission_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.