json_repair
Takes JSON that almost parses and makes it parse: markdown code fences, prose wrapped around the object, trailing commas, single or smart quotes, unquoted keys, Python True/False/None, comments, NaN, and brackets left open by a truncated response. Every change is reported, so the caller learns wh...
This record as markdown: /tools/com-fluentedi-tools/json-repair.md
What json_repair does on Tools
AI agents call json_repair to retrieve information from Tools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
input | string | Yes | The malformed JSON text. |
close_truncated | boolean | — | Close brackets left open by a cut-off response. |
Parameters from the server's own tool schema.
Why json_repair is rated Low
Even though json_repair only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs json_repair safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For json_repair, this is the rule to start with:
json_repair is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tools, apply this rule, and every json_repair call is checked against it from then on.
Questions about json_repair
Takes JSON that almost parses and makes it parse: markdown code fences, prose wrapped around the object, trailing commas, single or smart quotes, unquoted keys, Python True/False/None, comments, NaN, and brackets left open by a truncated response. Every change is reported, so the caller learns what its generator got wrong rather than silently depending on a fixer. When the input cannot be salvaged it returns the precise line, column and a caret pointing at the offending character — which is what makes the next attempt succeed instead of guessing. It is categorised as a Read tool in the Tools MCP Server, which means it retrieves data without modifying state.
json_repair accepts 2 parameters: input, close_truncated. Required: input. The full parameter table on this page comes from the server's own tool schema.
Register the Tools MCP server in PolicyLayer and add a rule for json_repair: 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 Tools. Nothing to install.
json_repair 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_repair 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_repair. 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_repair is provided by the Tools MCP server (https://fluentedi.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tools, and thousands of servers like it.
This server
Across the catalogue