Search crontab entries containing a keyword (case-insensitive).
AI agents call search_crontab 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 only queries and retrieves existing crontab data based on search criteria. It does not create, modify, execute, or delete any crontab entries. The sibling tools indicate this server manages crontab operations (add, remove, execute), but search_crontab is strictly a read operation.
From the tool's definition Tool performs a search query on crontab entries to retrieve matching results. The description states it searches for entries containing a keyword, which is a read-only retrieval operation with no modification or execution of scheduled tasks.
Attacks that exploit this kind of access
Search crontab entries containing a keyword (case-insensitive). 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 search_crontab: 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.
search_crontab 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 search_crontab 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 search_crontab. 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.
search_crontab 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.
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 →