move_context · OCD - Organized Context Datastore (MCP) MCP

WHAT IT DOES

What move_context does on OCD - Organized Context Datastore (MCP)

AI agents use move_context to create or update resources in OCD - Organized Context Datastore (MCP) — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OCD - Organized Context Datastore (MCP) environment.

WHY IT NEEDS A POLICY

Why move_context needs a policy

This tool modifies the organizational structure and possibly names of stored contexts within the persistent memory system. While reversible (contexts can be moved again or renamed back), it constitutes a Write operation that alters metadata and hierarchy.

From the tool's definition Tool name 'move_context' and description indicate it moves/renames contexts. The description states '配列対応: 複数一括移動可能' (supports arrays: can move multiple items in batch). Moving and renaming are reversible modifications to the data structure.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_context Rate-limited

move_context 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_context": {
      "limits": [
        {
          "counter": "move_context_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 OCD - Organized Context Datastore (MCP), so you can run agents against it safely.

FAQ

Questions about move_context

What does the move_context tool do? +

コンテキストを移動/リネームします (配列対応: 複数一括移動可能). It is categorised as a Write tool in the OCD - Organized Context Datastore (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_context? +

Register the OCD - Organized Context Datastore (MCP) MCP server in PolicyLayer and add a rule for move_context: 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 OCD - Organized Context Datastore (MCP). Nothing to install.

What risk level is move_context? +

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

Can I rate-limit move_context? +

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

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

move_context is provided by the OCD - Organized Context Datastore (MCP) MCP server (teamstove/organized-context-datastore-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.