Link two entities together (e.g. link a contact to a lead, or a company to a lead).
AI agents use link_entities to create or update resources in Kommo MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kommo MCP Server environment.
Linking entities modifies the state of CRM records by creating associations between them, which is a Write operation (creates/modifies data reversibly). This is not Read (no pure querying), not Execute (no arbitrary code/commands), not Destructive (the link can be removed), and not Financial (no money movement).
From the tool's definition Tool description states 'Link two entities together (e.g. link a contact to a lead, or a company to a lead)' — this creates a relationship or association between entities, which is a reversible modification of data structure.
Attacks that exploit this kind of access
Link two entities together (e.g. link a contact to a lead, or a company to a lead). It is categorised as a Write tool in the Kommo MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kommo MCP Server MCP server in PolicyLayer and add a rule for link_entities: 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 Kommo MCP Server. Nothing to install.
link_entities 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 link_entities 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 link_entities. 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.
link_entities is provided by the Kommo MCP Server MCP server (wdavidce/kommo-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 →