create_task
Create a task. Optionally link to a CRM account or assign to a team member.
This record as markdown: /tools/io-favcrm-favcrm/create-task.md
What create_task does on FavCRM
AI agents use create_task to create or update resources in FavCRM, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FavCRM environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
title | string | Yes | Task title |
status | string | — | Status filter |
dueDate | string | — | ISO date (YYYY-MM-DD) |
priority | string | — | Priority |
accountId | string | — | Linked CRM account |
assigneeId | string | — | company_members.id |
description | string | — | Description |
Parameters from the server's own tool schema.
Why create_task is rated Medium
This tool creates new task records in the CRM system, which is a reversible write operation. While tasks are business-critical in a service CRM, the action itself is straightforward data creation (Write category). Severity is medium because misuse could create spam tasks, clutter workflows, or assign erroneous work, but the impact is limited to task records and reversible via deletion or updates.
From the tool's definition Tool performs a create operation: 'Create a task'. The description explicitly states task creation with optional linking and assignment, indicating persistent data modification without deletion or execution of external code.
Attacks that exploit this kind of access
The rule that runs create_task safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FavCRM, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_task, this is the rule to start with:
create_task stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect FavCRM, apply this rule, and every create_task call is checked against it from then on.
Questions about create_task
Create a task. Optionally link to a CRM account or assign to a team member. It is categorised as a Write tool in the FavCRM MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_task accepts 7 parameters: title, status, dueDate, priority, accountId, assigneeId, description. Required: title. The full parameter table on this page comes from the server's own tool schema.
Register the FavCRM 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 FavCRM. 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 FavCRM MCP server (https://api.favcrm.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FavCRM, and thousands of servers like it.
This server
Across the catalogue