create_context · OCD - Organized Context Datastore (MCP) MCP

WHAT IT DOES

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

AI agents use create_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 create_context needs a policy

The tool creates new data structures (contexts) in the OCD datastore, which is reversible via complementary delete_context operations. This fits the Write category—it produces side effects but does not delete, destroy, or execute arbitrary code.

From the tool's definition Tool description indicates creation of new contexts ("新規コンテキストを作成します" = 'Create new context'). This is a write operation that modifies the persistent datastore by adding new entries.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_context Rate-limited

create_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": {
    "create_context": {
      "limits": [
        {
          "counter": "create_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 create_context

What does the create_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 create_context? +

Register the OCD - Organized Context Datastore (MCP) MCP server in PolicyLayer and add a rule for create_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 create_context? +

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

Can I rate-limit create_context? +

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

Set action: deny in the PolicyLayer policy for create_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 create_context? +

create_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.