List the cron jobs (crontab entries) on a server
AI agents call list_crons 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.
This tool retrieves information about existing cron jobs without creating, modifying, deleting, or executing them. It has no side effects and poses minimal risk as it only exposes scheduling metadata that an authorized user would typically have access to on their own infrastructure.
From the tool's definition Tool name is 'list_crons' and description states it 'List the cron jobs (crontab entries) on a server' — a pure query operation with no modification, deletion, or execution of cron jobs.
Attacks that exploit this kind of access
List the cron jobs (crontab entries) 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_crons: 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_crons 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_crons 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_crons. 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_crons 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 →