Pretty-print a JSON object with sorted keys.
AI agents call json_pretty to retrieve information from Mdb Mcp Gateway without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reformats and displays data; it does not create, modify, delete, execute code, move funds, or trigger external operations. It is a safe utility for rendering JSON in human-readable form.
From the tool's definition Tool performs JSON pretty-printing with key sorting - a pure data formatting operation with no mutations, side effects, or external calls. Description explicitly states it 'pretty-print[s] a JSON object', indicating read-only transformation of input data.
Attacks that exploit this kind of access
Pretty-print a JSON object with sorted keys. It is categorised as a Read tool in the Mdb Mcp Gateway MCP Server, which means it retrieves data without modifying state.
Register the Mdb Mcp Gateway MCP server in PolicyLayer and add a rule for json_pretty: 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 Mdb Mcp Gateway. Nothing to install.
json_pretty 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_pretty 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_pretty. 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_pretty is provided by the Mdb Mcp Gateway MCP server (ranfysvalle02/m-gate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →