AI agents use move_task to create or update resources in Proofhub — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Proofhub environment.
Moving a task between todolists and projects is a reversible modification operation. It changes metadata/associations but does not delete data, execute arbitrary code, or trigger financial operations. The severity is medium because inadvertent mass moves could disorganize workflows, but the action is reversible and has limited blast radius compared to destructive operations.
From the tool's definition Tool description states 'Move a task to a different todolist (and optionally a different project)' - this modifies the state and organizational structure of a task by changing its parent todolist/project associations.
Attacks that exploit this kind of access
Move a task to a different todolist (and optionally a different project). project and todolist default to context. It is categorised as a Write tool in the Proofhub MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Proofhub 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 Proofhub. Nothing to install.
move_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 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.
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.
move_task is provided by the Proofhub MCP server (yashmody/proofhub-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
move_task is one line of Proofhub's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →