Search mission templates by natural-language query. Returns ranked templates with slug, version, title, description, paramSchema, and match reasons. Ranking combines keyword relevance with live success-rate signal from providerHealth — templates whose steps call providers that have been degrading...
AI agents call discover_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.
discover_missions retrieves and returns structured metadata about mission templates—a pure read operation with no data modification, execution, or side effects. However, the severity is elevated to 'medium' rather than 'low' because: (1) the tool provides access to paramSchema and template details that could be reconnaissance for exploiting downstream APIs; (2) an AI agent could use this to discover mission…
From the tool's definition discover_missions: 'Search mission templates by natural-language query. Returns ranked templates with slug, version, title, description, paramSchema, and match reasons.'
Documented attack patterns abuse exactly the kind of access discover_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 discover_missions:
{
"version": "1",
"default": "deny",
"tools": {
"discover_missions": {}
}
}discover_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.
Search mission templates by natural-language query. Returns ranked templates with slug, version, title, description, paramSchema, and match reasons. Ranking combines keyword relevance with live success-rate signal from providerHealth — templates whose steps call providers that have been degrading in the last 30 days slide down automatically. Use this to find the right template by intent before calling 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 discover_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.
discover_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 discover_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 discover_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.
discover_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.