Create a new phone record
AI agents use create_phone to create or update resources in CiviCRM MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CiviCRM MCP Server environment.
The tool creates a new phone record, which is a reversible write operation. It adds data to the system without deleting or modifying existing records. The severity is medium rather than low because phone records in a CRM may be used for contact purposes and could enable unwanted communications if created with incorrect data, though the operation is fully reversible by deleting the phone record.
From the tool's definition Tool name is 'create_phone' and description states 'Create a new phone record'. This explicitly creates new data in the CiviCRM system.
Attacks that exploit this kind of access
Create a new phone record. It is categorised as a Write tool in the CiviCRM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CiviCRM MCP Server MCP server in PolicyLayer and add a rule for create_phone: 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 CiviCRM MCP Server. Nothing to install.
create_phone 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 create_phone 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 create_phone. 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.
create_phone is provided by the CiviCRM MCP Server MCP server (johncallhub/civicrm-mcp-server). 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 →