Low Risk

json_diff

Compare two JSON structures and return differences

How to control json_diff ↓

What json_diff does on Postgres Mcp Legacy

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

Low Risk

Why json_diff needs a policy

This tool performs a comparison operation that retrieves and analyzes data without creating, modifying, executing, or deleting anything. It is analogous to a diff utility, which is a read-only diagnostic tool. Misuse poses minimal risk—an agent could only waste compute time or learn about structural differences in JSON data it already has access to.

From the tool's definition Tool description states it 'Compare[s] two JSON structures and return[s] differences' — a query operation with no side effects. The name 'json_diff' and function signature indicate retrieval and analysis only.

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

How to control json_diff

PolicyLayer is an MCP gateway — it sits between your AI agents and Postgres Mcp Legacy, and nothing reaches the server without passing your rules. This is the rule we recommend for json_diff:

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

json_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 Postgres Mcp Legacy — 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 json_diff

What does the json_diff tool do? +

Compare two JSON structures and return differences. It is categorised as a Read tool in the Postgres Mcp Legacy MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on json_diff? +

Register the Postgres Mcp Legacy MCP server in PolicyLayer and add a rule for json_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 Postgres Mcp Legacy. Nothing to install.

What risk level is json_diff? +

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

Can I rate-limit json_diff? +

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

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

json_diff is provided by the Postgres Mcp Legacy MCP server (neverinfamous/postgres-mcp-legacy). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Postgres Mcp Legacy tool call.

Start from Postgres Mcp Legacy, 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.

60 Postgres Mcp Legacy 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.