New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

update_task

Update fields on an existing task. Only provided fields change.

SERVERFeatureBoard SOURCEhttps://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about update_task

What does the update_task tool do? +

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.

How do I enforce a policy on update_task? +

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.

What risk level is update_task? +

update_task is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_task? +

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.

How do I block update_task completely? +

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.

What MCP server provides update_task? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of FeatureBoard's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.