move_to_project · Things Cloud MCP: Risk & Policy

WHAT IT DOES

What move_to_project does on Things Cloud MCP

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

WHY IT NEEDS A POLICY

Why move_to_project needs a policy

Moving a task to a different project is a reversible modification of task metadata. It does not delete data (Destructive), execute arbitrary code (Execute), or involve financial transactions (Financial). The change can be undone by moving the task back to its original project or elsewhere.

From the tool's definition Tool description states 'Move a task into a project' — this modifies task state by changing its parent project association.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_to_project Rate-limited

move_to_project 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_to_project": {
      "limits": [
        {
          "counter": "move_to_project_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 Things Cloud MCP, so you can run agents against it safely.

FAQ

Questions about move_to_project

What does the move_to_project tool do? +

Move a task into a project. It is categorised as a Write tool in the Things Cloud MCP 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_to_project? +

Register the Things Cloud MCP server in PolicyLayer and add a rule for move_to_project: 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 Things Cloud MCP. Nothing to install.

What risk level is move_to_project? +

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

Can I rate-limit move_to_project? +

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

Set action: deny in the PolicyLayer policy for move_to_project. 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_to_project? +

move_to_project is provided by the Things Cloud MCP server (nkootstra/things). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.