List the daemons (long-running processes like queue:work) on a server
AI agents call list_daemons to retrieve information from Ploi MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a read-only operation to retrieve and display a list of existing daemons on a server. It has no side effects, does not modify state, and merely queries existing data. This is a straightforward Read category tool with low severity since it only exposes visibility into server processes without the ability to create, modify, or delete them.
From the tool's definition Tool name contains 'list' and description states 'List the daemons' with no modification, creation, or deletion capability. This is a query operation that retrieves daemon information.
Attacks that exploit this kind of access
List the daemons (long-running processes like queue:work) on a server. It is categorised as a Read tool in the Ploi MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Ploi MCP Server MCP server in PolicyLayer and add a rule for list_daemons: 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 Ploi MCP Server. Nothing to install.
list_daemons 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_daemons 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_daemons. 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_daemons is provided by the Ploi MCP Server MCP server (sudanese/ploi-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 →