update_contact_tool
AI agents use update_contact_tool 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.
The tool name 'update_contact_tool' clearly indicates creation or modification of data in a reversible manner, fitting the Write category. Severity is medium because unauthorized contact updates could lead to corrupted customer data, lost communications, or compliance issues in CRM systems, but the blast radius is bounded to contact records unless the tool permits batch operations.
From the tool's definition Tool named 'update_contact_tool' with no description provided. The name indicates modification of contact data in Zoho CRM.
Attacks that exploit this kind of access
update_contact_tool. 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 update_contact_tool: 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.
update_contact_tool 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 update_contact_tool 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 update_contact_tool. 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.
update_contact_tool is provided by the Zoho CRM MCP Server MCP server (skanderbs2024/zoho-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 →