crow_pm_plan_export

Export all approved events NOW as one planned-events feed file in the configured Drive folder (instead of waiting for the planner cron). Each event is exported exactly once.

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-pm-plan-export.md

WHAT IT DOES

What crow_pm_plan_export does on Crow

AI agents use crow_pm_plan_export 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_pm_plan_export is rated Medium

An AI agent can call crow_pm_plan_export faster than any human can review: one bad instruction and it creates or modifies resources in Crow by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

crow_pm_plan_export Rate-limited

crow_pm_plan_export 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_pm_plan_export": {
      "limits": [
        {
          "counter": "crow_pm_plan_export_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_pm_plan_export call is checked against it from then on.

FAQ

Questions about crow_pm_plan_export

What does the crow_pm_plan_export tool do? +

Export all approved events NOW as one planned-events feed file in the configured Drive folder (instead of waiting for the planner cron). Each event is exported exactly once. 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_pm_plan_export? +

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

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

Can I rate-limit crow_pm_plan_export? +

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

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

crow_pm_plan_export 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

team_manager_plan_room on Team Manager MCP → The MCP Attack Database →

Guides

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