update_pipeline_card · Keycrm MCP: Risk & Policy

WHAT IT DOES

What update_pipeline_card does on Keycrm

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

WHY IT NEEDS A POLICY

Why update_pipeline_card needs a policy

The tool modifies existing pipeline records (stage transitions, contact updates, notes) but does not delete or destroy data irreversibly, and does not involve financial transactions. This is a Write operation: it creates or modifies data reversibly.

From the tool's definition Tool description states 'Update an existing pipeline card (move stage, update contact, add notes, etc.)' — these are reversible modifications to pipeline data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_pipeline_card Rate-limited

update_pipeline_card 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": {
    "update_pipeline_card": {
      "limits": [
        {
          "counter": "update_pipeline_card_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Keycrm, so you can run agents against it safely.

FAQ

Questions about update_pipeline_card

What does the update_pipeline_card tool do? +

Update an existing pipeline card (move stage, update contact, add notes, etc.). It is categorised as a Write tool in the Keycrm MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_pipeline_card? +

Register the Keycrm MCP server in PolicyLayer and add a rule for update_pipeline_card: 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 Keycrm. Nothing to install.

What risk level is update_pipeline_card? +

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

Can I rate-limit update_pipeline_card? +

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

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

update_pipeline_card is provided by the Keycrm MCP server (ivanklymenko/keycrm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.