kommo_api_request · Kommo MCP Server MCP: Risk & Policy

WHAT IT DOES

What kommo_api_request does on Kommo MCP Server

AI agents invoke kommo_api_request to trigger actions in Kommo 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.

WHY IT NEEDS A POLICY

Why kommo_api_request needs a policy

This tool is a generic HTTP request executor that can invoke any Kommo API endpoint with any method (GET, POST, PUT, DELETE, etc.). Because it permits arbitrary operations including deletions, modifications, and creations across the entire Kommo CRM API surface, it spans Read through Destructive. Per the rules, the most severe applicable category is chosen.

From the tool's definition "Make a raw custom HTTP request to the Kommo v4 API. VERY POWERFUL: Use this to interact with any Kommo API endpoint"

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

kommo_api_request Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "kommo_api_request": {
      "limits": [
        {
          "counter": "kommo_api_request_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Kommo MCP Server, so you can run agents against it safely.

FAQ

Questions about kommo_api_request

What does the kommo_api_request tool do? +

Make a raw custom HTTP request to the Kommo v4 API. VERY POWERFUL: Use this to interact with any Kommo API endpoint (custom fields, notes, tasks, advanced lead filtering) after reading the Kommo official documentation. It is categorised as a Execute tool in the Kommo MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on kommo_api_request? +

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

What risk level is kommo_api_request? +

kommo_api_request is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit kommo_api_request? +

Yes. Add a rate_limit block to the kommo_api_request 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 kommo_api_request completely? +

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

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