crm_update_lead · Medicus CRM MCP Server MCP: Risk & Policy

WHAT IT DOES

What crm_update_lead does on Medicus CRM MCP Server

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

WHY IT NEEDS A POLICY

Why crm_update_lead needs a policy

The tool creates or modifies data reversibly by updating lead records. It does not execute arbitrary code, delete data, or commit financial transactions. The 'Update' action is characteristic of Write category operations. Severity is medium because unintended lead modifications could impact business processes and data integrity, but changes are typically reversible through subsequent updates or system backups.

From the tool's definition Tool name 'crm_update_lead' and description 'Update any allowed fields on a lead' explicitly indicate modification of existing data records in the CRM system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

crm_update_lead Rate-limited

crm_update_lead 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": {
    "crm_update_lead": {
      "limits": [
        {
          "counter": "crm_update_lead_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 Medicus CRM MCP Server, so you can run agents against it safely.

FAQ

Questions about crm_update_lead

What does the crm_update_lead tool do? +

Update any allowed fields on a lead. It is categorised as a Write tool in the Medicus CRM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on crm_update_lead? +

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

What risk level is crm_update_lead? +

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

Can I rate-limit crm_update_lead? +

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

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

crm_update_lead is provided by the Medicus CRM MCP Server MCP server (soundrolling/crmmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.