List all active automations (cron jobs, webhooks, monitors)
AI agents call list_automations to retrieve information from ClawDaemon MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool itself is a read-only enumeration (list). Severity is medium rather than low because: (1) the server enables persistent, background automation that could be weaponized if an agent gains control of it, (2) listing active automations reveals the attack surface and scope of what's currently executing, and (3) an agent querying this could identify high-value automation targets to manipulate or exploit via…
From the tool's definition Tool name 'list_automations' and description 'List all active automations' indicate a query/retrieval operation with no modifications.
Attacks that exploit this kind of access
List all active automations (cron jobs, webhooks, monitors). It is categorised as a Read tool in the ClawDaemon MCP MCP Server, which means it retrieves data without modifying state.
Register the ClawDaemon MCP server in PolicyLayer and add a rule for list_automations: 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 ClawDaemon MCP. Nothing to install.
list_automations 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_automations 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_automations. 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_automations is provided by the ClawDaemon MCP server (mordiaky/clawdaemon-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →