Create a new task (call, meeting, email) for a specific entity (lead, contact).
AI agents use create_task 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.
This tool creates new task records in the CRM system (calls, meetings, emails) associated with leads or contacts. Creation of data is Write-category behavior. Severity is medium rather than low because tasks can affect business workflows and communication tracking, though the action is reversible (tasks can be deleted or modified).
From the tool's definition Tool description states 'Create a new task' which is a data creation operation. The types enumerated (call, meeting, email) are reversible actions that create records in the CRM system.
Attacks that exploit this kind of access
Create a new task (call, meeting, email) for a specific entity (lead, contact). 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_task: 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_task 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_task 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_task. 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_task 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 →