move_collection_item · AI-Canvas MCP Server MCP

WHAT IT DOES

What move_collection_item does on AI-Canvas MCP Server

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

WHY IT NEEDS A POLICY

Why move_collection_item needs a policy

This tool creates or modifies data reversibly: it changes where a design asset lives within the system's collection hierarchy and may create new collections on demand. The action is reversible (items can be moved back), so it does not qualify as Destructive. It does not execute arbitrary code, trigger external operations, or involve financial transactions.

From the tool's definition Tool description states 'Move a collection item from one collection to another (target created if missing)' — this modifies the organizational structure of design assets by relocating items between collections and can auto-create collections as a side effect.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_collection_item Rate-limited

move_collection_item 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_collection_item": {
      "limits": [
        {
          "counter": "move_collection_item_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 AI-Canvas MCP Server, so you can run agents against it safely.

FAQ

Questions about move_collection_item

What does the move_collection_item tool do? +

Move a collection item from one collection to another (target created if missing). It is categorised as a Write tool in the AI-Canvas 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_collection_item? +

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

What risk level is move_collection_item? +

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

Can I rate-limit move_collection_item? +

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

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

move_collection_item is provided by the AI-Canvas MCP Server MCP server (laoluojuhai/ai-canvas). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.