AI agents call crow_list_bot_schedules to retrieve information from Crow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that retrieves information about existing bot schedules. It has no side effects—it queries data without creating, modifying, deleting, or triggering any external actions. The blast radius of misuse is minimal, as an attacker could only gain visibility into what schedules exist, which is low-sensitivity information in a project management context.
From the tool's definition Tool name contains 'list' and description states 'List recurring bot-cron schedules'; the function retrieves and queries existing schedule data without modifying, deleting, or executing any operations.
Attacks that exploit this kind of access
List recurring bot-cron schedules (optionally filtered to one bot). It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.
Register the Crow MCP server in PolicyLayer and add a rule for crow_list_bot_schedules: 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 Crow. Nothing to install.
crow_list_bot_schedules 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 crow_list_bot_schedules 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 crow_list_bot_schedules. 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.
crow_list_bot_schedules is provided by the Crow MCP server (kh0pper/crow). 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 →