get_loss_reasons

THE RISK

Low Risk

Why get_loss_reasons needs a policy

This tool retrieves a static or semi-static reference list of loss reasons from the Kommo CRM API. It performs a read-only query with no side effects, no code execution, and no data modification or deletion. The blast radius of misuse is minimal—an attacker gains only informational data about why leads are typically lost, which is already known organizational metadata.

From the tool's definition Tool name 'get_loss_reasons' and description 'Obter lista de motivos da perda de leads' (Portuguese: 'Obtain list of reasons for loss of leads') indicate data retrieval only.

Documented attack patterns abuse exactly the kind of access get_loss_reasons gives an agent:

POLICY

How to control get_loss_reasons

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 get_loss_reasons:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_loss_reasons": {}
  }
}

get_loss_reasons is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Kommo CRM MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Kommo CRM MCP Server tools

Execute run_salesbot Iniciar um Salesbot (API v4). Requer entity_id e entity_type (ex.: leads). Execute stop_salesbot Parar um Salesbot pelo ID do bot Write unpin_note Desafixar uma nota no cartão da entidade Write add_note Adicionar uma nota de texto a lead, contato ou empresa Write create_lead Criar um novo lead no Kommo CRM Write create_task Criar uma nova tarefa vinculada a lead, contato ou empresa Write move_lead Mover lead para outro status ou pipeline Write pin_note Fixar uma nota no cartão da entidade (lead, contato ou empresa)

All 23 Kommo CRM MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_loss_reasons

What does the get_loss_reasons tool do? +

Obter lista de motivos da perda de leads (API 2026). It is categorised as a Read tool in the Kommo CRM MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_loss_reasons? +

Register the Kommo CRM MCP Server MCP server in PolicyLayer and add a rule for get_loss_reasons: 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.

What risk level is get_loss_reasons? +

get_loss_reasons is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_loss_reasons? +

Yes. Add a rate_limit block to the get_loss_reasons 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.

How do I block get_loss_reasons completely? +

Set action: deny in the PolicyLayer policy for get_loss_reasons. 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.

What MCP server provides get_loss_reasons? +

get_loss_reasons 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.

Enforce policy on every Kommo CRM MCP Server tool call.

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.

CHECK YOUR STACK →