Add or remove tags from a Kommo lead. Expects arrays
AI agents use manage_lead_tags 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.
This tool modifies lead data by adding or removing tags, which is a reversible write operation. It does not delete core records (Destructive), execute arbitrary code (Execute), or involve financial transactions (Financial). The blast radius is medium because incorrect tag management could affect lead organization, filtering, and workflows, but changes are reversible.
From the tool's definition Tool description states 'Add or remove tags from a Kommo lead', indicating modification of lead metadata through write operations. The verb 'add' and 'remove' confirm reversible data mutations.
Attacks that exploit this kind of access
Add or remove tags from a Kommo lead. Expects arrays. 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 manage_lead_tags: 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.
manage_lead_tags 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 manage_lead_tags 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 manage_lead_tags. 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.
manage_lead_tags 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 →