AI agents call json_diff to retrieve information from TinyFn without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
json1 | string | Yes | First JSON string |
json2 | string | Yes | Second JSON string |
Parameters from the server's own tool schema.
json_diff performs a read-only comparison and returns the differences between two JSON inputs. It has no side effects, does not create, modify, or delete data, and does not execute external operations. This is a classic Read category tool: it retrieves or queries data for analysis purposes. Low severity reflects minimal blast radius if misused by an AI agent — worst case is incorrect or redundant diff output.
From the tool's definition Tool name and description indicate it 'Compare[s] two JSON objects and find differences' — a pure comparison/analysis operation with no modification, deletion, or execution of code.
Attacks that exploit this kind of access
Compare two JSON objects and find differences. It is categorised as a Read tool in the TinyFn MCP Server, which means it retrieves data without modifying state.
json_diff accepts 2 parameters: json1, json2. Required: json1, json2. The full parameter table on this page comes from the server's own tool schema.
Register the TinyFn 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 TinyFn. Nothing to install.
json_diff is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
json_diff is provided by the TinyFn MCP server (https://api.tinyfn.io/mcp/all/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
json_diff is one line of TinyFn's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →