List recent missions in the current workspace (most recent first).
AI agents call list_missions 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 performs a simple retrieval operation that queries mission metadata from the current workspace and returns results ordered by recency. It has no side effects, does not modify data, does not execute code or external operations, and does not involve financial transactions.
From the tool's definition The tool 'list_missions' retrieves/queries data about missions with description 'List recent missions in the current workspace (most recent first)'. The use of 'list' indicates a read operation with no modification, deletion, or execution of side effects.
Documented attack patterns abuse exactly the kind of access list_missions 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 list_missions:
{
"version": "1",
"default": "deny",
"tools": {
"list_missions": {}
}
}list_missions 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.
List recent missions in the current workspace (most recent first). 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 list_missions: 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.
list_missions 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 list_missions 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 list_missions. 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.
list_missions 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.