update_task
Update a task (status, priority, assignee, due date, completion).
This record as markdown: /tools/io-favcrm-favcrm/update-task.md
What update_task does on FavCRM
AI agents use update_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 | — | Title |
status | string | — | Status filter |
taskId | string | Yes | The task ID |
dueDate | string | — | Due date (ISO 8601) |
priority | string | — | Priority |
assigneeId | string | — | Assignee user ID |
description | string | — | Description |
Parameters from the server's own tool schema.
Why update_task is rated Medium
This tool creates or modifies data reversibly (the defining characteristic of Write category). Task updates are not destructive (data isn't deleted), not executable code/commands (Execute), not financial (Financial), and not read-only (Read). The severity is medium because task mismanagement could disrupt business operations and customer service workflows, but is typically recoverable through re-updates.
From the tool's definition Tool name 'update_task' and description explicitly states it modifies task attributes: 'status, priority, assignee, due date, completion'. These are reversible state changes within the CRM system.
Attacks that exploit this kind of access
The rule that runs update_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 update_task, this is the rule to start with:
update_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 update_task call is checked against it from then on.
Questions about update_task
Update a task (status, priority, assignee, due date, completion). 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.
update_task accepts 7 parameters: title, status, taskId, dueDate, priority, assigneeId, description. Required: taskId. 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 update_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.
update_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 update_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 update_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.
update_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