crow_schedule_bot
Schedule a Crow bot to run a goal on a recurring cron schedule. The result is delivered
This record as markdown: /tools/kh0pper-crow/crow-schedule-bot.md
What crow_schedule_bot does on Crow
AI agents invoke crow_schedule_bot to trigger actions in Crow. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why crow_schedule_bot is rated High
This tool schedules recurring automated bot executions, which constitutes triggering external operations. An AI agent misusing this could set up persistent, recurring automated actions that continuously execute goals, making it high severity due to the recurring and potentially unbounded nature of the scheduled executions.
From the tool's definition 'Schedule a Crow bot to run a goal on a recurring cron schedule' — triggers automated bot execution on a schedule
Attacks that exploit this kind of access
The rule that runs crow_schedule_bot safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crow_schedule_bot, this is the rule to start with:
crow_schedule_bot stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every crow_schedule_bot call is checked against it from then on.
Questions about crow_schedule_bot
Schedule a Crow bot to run a goal on a recurring cron schedule. The result is delivered. It is categorised as a Execute tool in the Crow MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Crow MCP server in PolicyLayer and add a rule for crow_schedule_bot: 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_schedule_bot is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the crow_schedule_bot 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_schedule_bot. 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_schedule_bot 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.
More on Crow, and thousands of servers like it.
This server
Across the catalogue