move_task · FacturaHub MCP Server MCP: Risk & Policy

WHAT IT DOES

What move_task does on FacturaHub MCP Server

AI agents use move_task to create or update resources in FacturaHub MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FacturaHub MCP Server environment.

WHY IT NEEDS A POLICY

Why move_task needs a policy

This is a write operation that reversibly updates task metadata. While it changes data, the transitions are constrained and non-destructive (tasks are not deleted; only their workflow status changes). The severity is low because task status changes have minimal blast radius—typical misuse would only affect internal workflow tracking, not financial systems, inventory, or critical data deletion.

From the tool's definition Tool description states "Move a task to a new status" with defined state transitions (backlog → todo, todo → in_progress, etc.). This modifies task state reversibly without deleting data or executing arbitrary code.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_task Rate-limited

move_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "move_task": {
      "limits": [
        {
          "counter": "move_task_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches FacturaHub MCP Server, so you can run agents against it safely.

FAQ

Questions about move_task

What does the move_task tool do? +

[FacturaHub] Move a task to a new status. Valid transitions: • backlog → todo • todo → in_progress, backlog • in_progress → review, todo • review → done, in_progress • done → (no transitions). It is categorised as a Write tool in the FacturaHub MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on move_task? +

Register the FacturaHub MCP Server MCP server in PolicyLayer and add a rule for move_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 FacturaHub MCP Server. Nothing to install.

What risk level is move_task? +

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

Can I rate-limit move_task? +

Yes. Add a rate_limit block to the move_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 move_task completely? +

Set action: deny in the PolicyLayer policy for move_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 move_task? +

move_task is provided by the FacturaHub MCP Server MCP server (santy1422/facturahub-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.