Low Risk

ingest_diff

Ingest a code diff/patch into the context memory. Converts a unified diff (git diff output) into a structured change summary: intent classification (bug-fix/feature/refactor), symbols changed, files modified, and line delta. Particularly useful for understanding recent changes and their architect...

How to control ingest_diff ↓

What ingest_diff does on Entroly Context Engine

AI agents call ingest_diff to retrieve information from Entroly Context Engine without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why ingest_diff needs a policy

This tool reads and analyzes code diffs to extract structured information (intent, symbols, files, line changes) for storage in context memory. While it processes code changes, it does not execute, modify, delete, or deploy code—it only parses and summarizes them. The 'ingest' operation is read-semantic (acquiring and analyzing data).

From the tool's definition Ingest a code diff/patch into the context memory. Converts a unified diff (git diff output) into a structured change summary: intent classification, symbols changed, files modified, and line delta.

Documented attack patterns abuse exactly the kind of access ingest_diff gives an agent:

How to control ingest_diff

PolicyLayer is an MCP gateway — it sits between your AI agents and Entroly Context Engine, and nothing reaches the server without passing your rules. This is the rule we recommend for ingest_diff:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "ingest_diff": {}
  }
}

ingest_diff is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Entroly Context Engine — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about ingest_diff

What does the ingest_diff tool do? +

Ingest a code diff/patch into the context memory. Converts a unified diff (git diff output) into a structured change summary: intent classification (bug-fix/feature/refactor), symbols changed, files modified, and line delta. Particularly useful for understanding recent changes and their architectural impact. Args: diff_text: Raw unified diff text (git diff output). source: Identifier (e.g., 'pr_42_auth_refactor.diff'). commit_message: Optional commit message for better intent classification. Returns JSON with ingestion result plus: - intent: bug-fix/feature/refactor/test/security/performance - files_changed, added_lines, removed_lines - symbols_changed: functions/classes modified. It is categorised as a Read tool in the Entroly Context Engine MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ingest_diff? +

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

What risk level is ingest_diff? +

ingest_diff is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit ingest_diff? +

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

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

ingest_diff is provided by the Entroly Context Engine MCP server (juyterman1000/entroly). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Entroly Context Engine tool call.

Start from Entroly Context Engine, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

52 Entroly Context Engine tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.