Create one or more records in the given module.
AI agents use create_record to create or update resources in Zoho CRM MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zoho CRM MCP Server environment.
This tool creates new records in Zoho CRM modules, which constitutes data modification. While creation is reversible (records can be deleted), the high severity reflects the potential for an AI agent to create unwanted records at scale ('one or more records'), pollute the CRM database, or create records with sensitive/incorrect information that could impact business operations.
From the tool's definition Tool description states it will 'Create one or more records in the given module.' The capability to create records in a CRM system is a Write operation that modifies data in a reversible manner.
Attacks that exploit this kind of access
Create one or more records in the given module. It is categorised as a Write tool in the Zoho CRM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Zoho CRM MCP Server MCP server in PolicyLayer and add a rule for create_record: 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 Zoho CRM MCP Server. Nothing to install.
create_record 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_record 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_record. 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_record is provided by the Zoho CRM MCP Server MCP server (lokimcpuniverse/zoho-crm-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 →