Quickly move a task to a new status. Note: tasks must be in
AI agents use move_task_status to create or update resources in Flux MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Flux MCP Server environment.
This tool updates task metadata (status/state) on a Kanban board. It is reversible (a task can be moved back to a previous status), so it falls under Write rather than Destructive. Severity is medium because misuse could disrupt task workflows and project coordination, but changes are recoverable.
From the tool's definition Tool name 'move_task_status' and server description 'update... tasks on a Kanban board'. The action modifies task state (status field) reversibly—moving a task to a different status column is an update operation, not deletion.
Documented attack patterns abuse exactly the kind of access move_task_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Flux MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for move_task_status:
{
"version": "1",
"default": "deny",
"tools": {
"move_task_status": {
"limits": [
{
"counter": "move_task_status_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}move_task_status 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.
Free to start. No card required.
Quickly move a task to a new status. Note: tasks must be in. It is categorised as a Write tool in the Flux MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Flux MCP Server MCP server in PolicyLayer and add a rule for move_task_status: 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 Flux MCP Server. Nothing to install.
move_task_status 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 move_task_status 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 move_task_status. 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.
move_task_status is provided by the Flux MCP Server MCP server (sirsjg/flux). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 25 Flux MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
25 Flux MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.