Update or delete a scheduled task by ID. Provide only the fields you want to change, or set delete=true to remove it.
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.
While the tool permits deletion via the delete=true flag, the primary function described is update/modification of scheduled tasks. The deletion of a task is a specific, intentional operation (not a cascade or bulk destructive action) and scheduled task removal is typically reversible through restoration or recreation in project management systems. The most common use case is modification (Write).
From the tool's definition Tool description states 'Update or delete a scheduled task by ID' and 'set delete=true to remove it'. The update capability is reversible (Write), but the delete option makes this borderline Destructive.
Documented attack patterns abuse exactly the kind of access crow_update_schedule gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for crow_update_schedule:
{
"version": "1",
"default": "deny",
"tools": {
"crow_update_schedule": {
"limits": [
{
"counter": "crow_update_schedule_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
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.
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.
crow_update_schedule is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
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.
Start from Crow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.