crm_update_lead_status · Medicus CRM MCP Server MCP

WHAT IT DOES

What crm_update_lead_status does on Medicus CRM MCP Server

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

This tool modifies lead status/data within the CRM system. Updates are reversible operations (the status can be changed again), placing it in the Write category. Severity is medium because misuse could alter sales pipeline data affecting business processes, but the impact is limited to a single lead record and can be corrected.

From the tool's definition Tool name 'crm_update_lead_status' and description 'Update a lead' indicate modification of lead data. The verb 'update' and action context (CRM lead management) confirm reversible state change rather than deletion or execution of arbitrary operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

crm_update_lead_status Rate-limited

crm_update_lead_status 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_status": {
      "limits": [
        {
          "counter": "crm_update_lead_status_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_status

What does the crm_update_lead_status tool do? +

Update 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_status? +

Register the Medicus CRM MCP Server MCP server in PolicyLayer and add a rule for crm_update_lead_status: 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_status? +

crm_update_lead_status 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_status? +

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

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

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