update_task
Update fields on an existing task. Only provided fields change.
This record as markdown: /tools/ai-featureboard-featureboard/update-task.md
What update_task does on FeatureBoard
AI agents use update_task to create or update resources in FeatureBoard, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FeatureBoard environment.
Why update_task is rated Medium
This tool creates or modifies data in a reversible manner (Write category). It updates task fields without deleting data, and changes can be undone through further updates. The severity is medium because misuse could corrupt or misdirect task tracking in a project board, affecting team coordination, but the impact is limited to task metadata and the changes are reversible.
From the tool's definition The tool description states 'Update fields on an existing task. Only provided fields change.' This is a modification operation that changes existing data reversibly.
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 FeatureBoard, 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 FeatureBoard, apply this rule, and every update_task call is checked against it from then on.
Questions about update_task
Update fields on an existing task. Only provided fields change. It is categorised as a Write tool in the FeatureBoard MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the FeatureBoard 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 FeatureBoard. 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 FeatureBoard MCP server (https://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FeatureBoard, and thousands of servers like it.
This server
Across the catalogue