Get recent cron execution logs from the system.
AI agents call get_cron_logs to retrieve information from Mcp Crontab without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical cron execution logs, which is a read-only operation with no side effects. It does not create, modify, delete, or execute anything—it only queries and returns log information. The severity is low because even if an agent accesses logs it shouldn't, the impact is information disclosure rather than system compromise or data loss.
From the tool's definition Tool name 'get_cron_logs' and description 'Get recent cron execution logs from the system' indicate retrieval of existing log data with no modification or deletion of logs.
Attacks that exploit this kind of access
Get recent cron execution logs from the system. It is categorised as a Read tool in the Mcp Crontab MCP Server, which means it retrieves data without modifying state.
Register the Mcp Crontab MCP server in PolicyLayer and add a rule for get_cron_logs: 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 Mcp Crontab. Nothing to install.
get_cron_logs 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 get_cron_logs 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 get_cron_logs. 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.
get_cron_logs is provided by the Mcp Crontab MCP server (jasona7/mcp-crontab-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_cron_logs is one line of Mcp Crontab's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →