dev.diff-json

Structured deep diff of two JSON values. POST { a, b }. Returns a list of changes, each with a dot-path and type (added / removed / changed) plus from/to values, and a total change count. For change-detection, config drift, and review tooling.

Server Mcp @2sio/mcp
Category Read
Risk class Low
Parameters 00 required

What dev.diff-json does on Mcp

AI agents call dev.diff-json to retrieve information from Mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why dev.diff-json needs a policy

This is a comparison and analysis tool with no side effects. It reads two JSON structures and produces a report of their differences. It neither modifies data, executes code, deletes anything, nor moves money. The use cases cited ('change-detection, config drift, and review tooling') all imply passive inspection.

From the tool's definition Tool description states it 'Returns a list of changes' from comparing two JSON inputs with 'dot-path and type (added / removed / changed) plus from/to values'.

Questions about dev.diff-json

What does the dev.diff-json tool do? +

Structured deep diff of two JSON values. POST { a, b }. Returns a list of changes, each with a dot-path and type (added / removed / changed) plus from/to values, and a total change count. For change-detection, config drift, and review tooling. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on dev.diff-json? +

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

What risk level is dev.diff-json? +

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

Can I rate-limit dev.diff-json? +

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

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

dev.diff-json is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.