Create a new webhook to receive real-time events from Kommo.
AI agents use create_webhook 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.
The tool creates a new webhook endpoint registration in Kommo CRM, which modifies system configuration state. While webhooks themselves are integrations for receiving events (not destructive), their creation constitutes a Write operation as it adds new data/configuration to the system that can be modified or removed later.
From the tool's definition create_webhook" with description "Create a new webhook to receive real-time events from Kommo" - this creates a new webhook configuration in the CRM system, a reversible modification to system integration settings.
Attacks that exploit this kind of access
Create a new webhook to receive real-time events from Kommo. 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 create_webhook: 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.
create_webhook 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 create_webhook 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 create_webhook. 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.
create_webhook 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 →