AI agents use move_lead to create or update resources in Kommo CRM MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kommo CRM MCP Server environment.
This tool modifies lead records by changing their status or pipeline assignment. This is a reversible write operation — the lead's previous state can be restored by moving it back. It does not delete data (would be Destructive), does not execute arbitrary code (would be Execute), and does not involve financial transactions (would be Financial).
From the tool's definition Tool name 'move_lead' and description 'Mover lead para outro status ou pipeline' (Move lead to another status or pipeline) indicates modification of lead data state without deletion.
Documented attack patterns abuse exactly the kind of access move_lead gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kommo CRM MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for move_lead:
{
"version": "1",
"default": "deny",
"tools": {
"move_lead": {
"limits": [
{
"counter": "move_lead_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}move_lead 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.
Mover lead para outro status ou pipeline. It is categorised as a Write tool in the Kommo CRM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kommo CRM MCP Server MCP server in PolicyLayer and add a rule for move_lead: 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 CRM MCP Server. Nothing to install.
move_lead 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 move_lead 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 move_lead. 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.
move_lead is provided by the Kommo CRM MCP Server MCP server (miguelgbastos/kommo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kommo CRM 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.
23 Kommo CRM MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.