bulk_update_products · Keycrm MCP: Risk & Policy

WHAT IT DOES

What bulk_update_products does on Keycrm

AI agents use bulk_update_products 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 bulk_update_products needs a policy

This is a Write operation (update/modify) affecting multiple records in the keyCRM catalogue. The bulk nature and potential for wide-reaching unintended changes (if filters are misconfigured) elevates severity to high, though the preview-and-confirm safeguards prevent automatic promotion to Destructive. Not Financial, Execute, or Destructive because updates are reversible and user-controlled.

From the tool's definition Tool description states 'Apply a field update to multiple products' — performs batch modifications to product data. Safe-by-default design with dry_run preview and confirmation requirements mitigates risk but does not eliminate it.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

bulk_update_products Rate-limited

bulk_update_products 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": {
    "bulk_update_products": {
      "limits": [
        {
          "counter": "bulk_update_products_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 bulk_update_products

What does the bulk_update_products tool do? +

Apply a field update to multiple products matching a filter. Call with dry_run:true first to preview, then dry_run:false and confirm:true to execute. 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 bulk_update_products? +

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

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

Can I rate-limit bulk_update_products? +

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

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

bulk_update_products 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.