crow_schedule_bot · Crow MCP: Risk & Policy

WHAT IT DOES

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 IT NEEDS A POLICY

Why crow_schedule_bot needs a policy

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

Recommended rule Ready

Verdict

crow_schedule_bot Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "crow_schedule_bot": {
      "limits": [
        {
          "counter": "crow_schedule_bot_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Crow, so you can run agents against it safely.

FAQ

Questions about crow_schedule_bot

What does the crow_schedule_bot tool do? +

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.

How do I enforce a policy on crow_schedule_bot? +

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.

What risk level is crow_schedule_bot? +

crow_schedule_bot is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit crow_schedule_bot? +

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.

How do I block crow_schedule_bot completely? +

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.

What MCP server provides crow_schedule_bot? +

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.