AI agents use create_record to create or update resources in MCP-Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP-Server environment.
The tool creates new data entries in Zoho CRM. This is a Write operation (reversible modification) rather than Read (no side effects), Execute (arbitrary operations), Destructive (irreversible deletion), or Financial. The severity is medium because creating records in a CRM can have business consequences, but the action is reversible via deletion or updates.
From the tool's definition Tool name 'create_record' combined with sibling tools 'add', 'bulk_create_records', 'update_record', and 'delete_record' clearly indicate this is a Zoho CRM integration server.
Documented attack patterns abuse exactly the kind of access create_record gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_record:
{
"version": "1",
"default": "deny",
"tools": {
"create_record": {
"limits": [
{
"counter": "create_record_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_record 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.
Free to start. No card required.
create_record. It is categorised as a Write tool in the MCP-Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 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 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 MCP-Server MCP server (officehub-tech-llc/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP-Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
9 MCP-Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.