context.build · Kelnix Datamind Curator MCP: Risk & Policy

WHAT IT DOES

What context.build does on Kelnix Datamind Curator

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

WHY IT NEEDS A POLICY

Why context.build needs a policy

Based on the tool name 'context.build' and the server's description which mentions 'build AI-ready context packages', this tool likely assembles or creates context packages from existing data. This maps to Write (creates data reversibly). However, the empty description significantly lowers confidence. It could also involve Execute-level operations if it triggers pipelines.

From the tool's definition Tool name: context.build; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

context.build Rate-limited

context.build 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": {
    "context.build": {
      "limits": [
        {
          "counter": "context.build_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 Kelnix Datamind Curator, so you can run agents against it safely.

FAQ

Questions about context.build

What does the context.build tool do? +

context.build. It is categorised as a Write tool in the Kelnix Datamind Curator MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on context.build? +

Register the Kelnix Datamind Curator MCP server in PolicyLayer and add a rule for context.build: 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 Kelnix Datamind Curator. Nothing to install.

What risk level is context.build? +

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

Can I rate-limit context.build? +

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

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

context.build is provided by the Kelnix Datamind Curator MCP server (kelnixsolutions/kelnix-datamind-curator). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.