AI agents invoke stop_salesbot to trigger actions in Kommo CRM MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an external operation (stopping an active bot/automation) rather than simply reading data or modifying records. While not destructive in the data sense, it interrupts a business-critical process. The severity is high because stopping a sales automation without proper authorization could disrupt revenue-generating workflows and customer interactions.
From the tool's definition Tool name 'stop_salesbot' with description 'Parar um Salesbot pelo ID do bot' (Stop a Salesbot by bot ID). The verb 'stop' indicates triggering an external operation (halting an automated bot process) whose effects depend on the bot ID argument provided.
Documented attack patterns abuse exactly the kind of access stop_salesbot 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 stop_salesbot:
{
"version": "1",
"default": "deny",
"tools": {
"stop_salesbot": {
"limits": [
{
"counter": "stop_salesbot_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}stop_salesbot stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Parar um Salesbot pelo ID do bot. It is categorised as a Execute tool in the Kommo CRM MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kommo CRM MCP Server MCP server in PolicyLayer and add a rule for stop_salesbot: 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.
stop_salesbot is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the stop_salesbot 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 stop_salesbot. 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.
stop_salesbot 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.