Get a list of cron jobs for a specific site.
AI agents call pressable_list_cron_jobs to retrieve information from Pressable MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves information about existing cron jobs for a site. It does not create, modify, delete, execute, or trigger any operations. The read-only nature and lack of side effects make this a low-severity Read operation. Even in the context of a WordPress management tool, listing cron jobs is purely informational and poses minimal risk.
From the tool's definition Tool name contains 'list' and description states 'Get a list of cron jobs' - classic read operation that retrieves and queries data with no side effects.
Attacks that exploit this kind of access
Get a list of cron jobs for a specific site. It is categorised as a Read tool in the Pressable MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Pressable MCP Server MCP server in PolicyLayer and add a rule for pressable_list_cron_jobs: 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 Pressable MCP Server. Nothing to install.
pressable_list_cron_jobs 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 pressable_list_cron_jobs 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 pressable_list_cron_jobs. 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.
pressable_list_cron_jobs is provided by the Pressable MCP Server MCP server (pcwprops/pressable-mcp-server). 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 →