ingest_record · Anchord MCP: Risk & Policy

WHAT IT DOES

What ingest_record does on Anchord MCP

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

WHY IT NEEDS A POLICY

Why ingest_record needs a policy

This tool creates or modifies data by ingesting source records into the Anchord system. It is reversible (records can be unlinked via unlink_source_record and presumably deleted), so it does not qualify as Destructive. It is not a read-only operation (get_entity, get_entity_export), nor does it execute arbitrary code or move money.

From the tool's definition Tool name is 'ingest_record' and description states 'Ingest a single source record into Anchord. The record is matched to an' (description appears truncated).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ingest_record Rate-limited

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

FAQ

Questions about ingest_record

What does the ingest_record tool do? +

Ingest a single source record into Anchord. The record is matched to an. It is categorised as a Write tool in the Anchord 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 ingest_record? +

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

What risk level is ingest_record? +

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

Can I rate-limit ingest_record? +

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

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

ingest_record is provided by the Anchord MCP server (nolenation04/anchord-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.