crow_update_schedule

Update or delete a scheduled task by ID. Provide only the fields you want to change, or set delete=true to remove it.

SERVERCrow SOURCEkh0pper/crow

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kh0pper-crow/crow-update-schedule.md

WHAT IT DOES

What crow_update_schedule does on Crow

AI agents use crow_update_schedule to create or update resources in Crow, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Crow environment.

RISK

Why crow_update_schedule is rated Medium

This tool primarily performs reversible write operations (updating scheduled task fields). While it includes a delete capability, the description emphasizes update functionality first. Deletion of scheduled tasks is less severe than destructive data operations since tasks can typically be recreated.

From the tool's definition Tool description states 'Update or delete a scheduled task by ID' with ability to modify fields or 'set delete=true to remove it.' The primary function is modification ('Update') via selective field changes, with deletion as a secondary option.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs crow_update_schedule 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_update_schedule, this is the rule to start with:

crow_update_schedule Rate-limited

crow_update_schedule stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_update_schedule": {
      "limits": [
        {
          "counter": "crow_update_schedule_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every crow_update_schedule call is checked against it from then on.

FAQ

Questions about crow_update_schedule

What does the crow_update_schedule tool do? +

Update or delete a scheduled task by ID. Provide only the fields you want to change, or set delete=true to remove it. It is categorised as a Write tool in the Crow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on crow_update_schedule? +

Register the Crow MCP server in PolicyLayer and add a rule for crow_update_schedule: 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_update_schedule? +

crow_update_schedule is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit crow_update_schedule? +

Yes. Add a rate_limit block to the crow_update_schedule 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_update_schedule completely? +

Set action: deny in the PolicyLayer policy for crow_update_schedule. 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_update_schedule? +

crow_update_schedule 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.

KEEP EXPLORING

More on Crow, and thousands of servers like it.

This server

All 587 Crow tools →

Across the catalogue

sms_schedule on Twilio SMS MCP Server →aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →