Create contact
AI agents use create_contact to create or update resources in Dolibarr MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dolibarr MCP Server environment.
This tool creates new contact records in the ERP/CRM system, which is a reversible write operation. While it modifies persistent data, contacts can be edited or deleted if needed. The severity is medium because creating unauthorized or fraudulent contacts could enable social engineering, spam, or identity fraud within the CRM, but the impact is limited compared to financial transactions or destructive operations.
From the tool's definition Tool name 'create_contact' and description 'Create contact' indicate a data creation operation that modifies the Dolibarr database by adding a new contact record.
Attacks that exploit this kind of access
Create contact. It is categorised as a Write tool in the Dolibarr MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Dolibarr MCP Server MCP server in PolicyLayer and add a rule for create_contact: 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 Dolibarr MCP Server. Nothing to install.
create_contact 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_contact 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_contact. 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_contact is provided by the Dolibarr MCP Server MCP server (marioser/dolibarr-mcp). 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 →