Create a new lead record.
AI agents use crm_create_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.
The tool creates (writes) a new lead record, which is a reversible operation typical of CRM data creation. It does not delete, execute arbitrary code, or involve financial transactions. The medium severity reflects that an agent could generate many spurious lead records, consuming resources or polluting the CRM database, but the operation itself is non-destructive and can be undone by deletion.
From the tool's definition Tool name 'crm_create_lead' and description 'Create a new lead record' indicate the tool creates new data in the CRM system. This is a reversible write operation that adds a record to the database without permanent deletion or destruction.
Attacks that exploit this kind of access
Create a new lead record. 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.
Register the Medicus CRM MCP Server MCP server in PolicyLayer and add a rule for crm_create_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.
crm_create_lead is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the crm_create_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.
Set action: deny in the PolicyLayer policy for crm_create_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.
crm_create_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →