move_items · Dynalist MCP: Risk & Policy

WHAT IT DOES

What move_items does on Dynalist

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

WHY IT NEEDS A POLICY

Why move_items needs a policy

Moving items within a document structure is a reversible write operation—items can be moved again to restore prior state. It modifies document organization but does not delete data (distinguishing it from Destructive) or execute arbitrary code (Execute). Medium severity reflects potential for organizational disruption if misused by an AI agent, but mitigated by reversibility.

From the tool's definition Tool name 'move_items' combined with sibling tools including 'delete_items', 'edit_items', and 'insert_items' on a document organization server indicates reversible data modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_items Rate-limited

move_items 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_items": {
      "limits": [
        {
          "counter": "move_items_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 Dynalist, so you can run agents against it safely.

FAQ

Questions about move_items

What does the move_items tool do? +

${INSTRUCTIONS_FIRST_GUIDANCE}. It is categorised as a Write tool in the Dynalist 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_items? +

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

What risk level is move_items? +

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

Can I rate-limit move_items? +

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

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

move_items is provided by the Dynalist MCP server (wawworld/dynalist-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.