crow_pm_plan_reconcile
Match exported events against the newest calendar ingest drop (marker category + subject + start ±5 min) and mark hits
This record as markdown: /tools/kh0pper-crow/crow-pm-plan-reconcile.md
What crow_pm_plan_reconcile does on Crow
AI agents use crow_pm_plan_reconcile 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.
Why crow_pm_plan_reconcile is rated Medium
The tool matches calendar events and marks them, which constitutes modification of existing data rather than deletion or irreversible destruction. While it updates state, these changes appear reversible and are limited to marking/tagging operations within a project management context.
From the tool's definition Tool performs 'mark hits' operation on calendar events, which is a data modification action. The description indicates it reconciles and updates state ('mark hits') of calendar entries based on matching criteria.
Attacks that exploit this kind of access
The rule that runs crow_pm_plan_reconcile 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_pm_plan_reconcile, this is the rule to start with:
crow_pm_plan_reconcile 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every crow_pm_plan_reconcile call is checked against it from then on.
Questions about crow_pm_plan_reconcile
Match exported events against the newest calendar ingest drop (marker category + subject + start ±5 min) and mark hits. 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_pm_plan_reconcile: 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_pm_plan_reconcile 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_pm_plan_reconcile 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_pm_plan_reconcile. 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_pm_plan_reconcile 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