List available Control Plane mission templates and the parameters each accepts.
AI agents call list_mission_templates 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 query/list operation to retrieve information about mission templates and their parameters. It has no side effects, does not execute code, does not modify data, and does not access or move financial resources. It is purely informational/read-only in nature, posing minimal risk if invoked by an AI agent.
From the tool's definition The tool is described as 'List available Control Plane mission templates' — a retrieval operation with no modification, creation, or execution of code/commands. It reads and returns metadata about available templates.
Documented attack patterns abuse exactly the kind of access list_mission_templates 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_mission_templates:
{
"version": "1",
"default": "deny",
"tools": {
"list_mission_templates": {}
}
} list_mission_templates 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 available Control Plane mission templates and the parameters each accepts. 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_mission_templates: 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_mission_templates 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_mission_templates 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_mission_templates. 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_mission_templates 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.