add_contexts_batch · Context MCP: Risk & Policy

WHAT IT DOES

What add_contexts_batch does on Context MCP

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

WHY IT NEEDS A POLICY

Why add_contexts_batch needs a policy

This tool creates and stores new semantic information in the vector database. While reversible (data can be deleted via delete_context or delete_contexts_batch), it modifies persistent state. The batch nature means a single misuse could add many unwanted entries, elevating severity from low to medium.

From the tool's definition Tool name 'add_contexts_batch' and description 'Add multiple context entries to the vector database in a single operation' explicitly indicate creation/modification of data. The 'batch' variant processes multiple entries at once, increasing blast radius.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_contexts_batch Rate-limited

add_contexts_batch 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": {
    "add_contexts_batch": {
      "limits": [
        {
          "counter": "add_contexts_batch_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 Context MCP, so you can run agents against it safely.

FAQ

Questions about add_contexts_batch

What does the add_contexts_batch tool do? +

Add multiple context entries to the vector database in a single operation. More efficient for bulk indexing. It is categorised as a Write tool in the Context 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 add_contexts_batch? +

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

What risk level is add_contexts_batch? +

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

Can I rate-limit add_contexts_batch? +

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

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

add_contexts_batch is provided by the Context MCP server (raunak-dev-18/context-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.