crow_pm_sync_run

Run one deterministic Monday.com sync pass over every board in the sync config (mirror boards pull into trackers; twoway boards three-way merge with the kanban tasks DB).

SERVERCrow SOURCEkh0pper/crow

High RISK CLASS

Category Execute

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-sync-run.md

WHAT IT DOES

What crow_pm_sync_run does on Crow

AI agents invoke crow_pm_sync_run 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.

RISK

Why crow_pm_sync_run is rated High

crow_pm_sync_run triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

crow_pm_sync_run Rate-limited

crow_pm_sync_run 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_pm_sync_run": {
      "limits": [
        {
          "counter": "crow_pm_sync_run_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_sync_run call is checked against it from then on.

FAQ

Questions about crow_pm_sync_run

What does the crow_pm_sync_run tool do? +

Run one deterministic Monday.com sync pass over every board in the sync config (mirror boards pull into trackers; twoway boards three-way merge with the kanban tasks DB). 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_pm_sync_run? +

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

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

Can I rate-limit crow_pm_sync_run? +

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

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

crow_pm_sync_run 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 → High-risk tools on this server →

Across the catalogue

shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →