Search for keys in a JSON file. Use when you do not know the path to a key in a large JSON file, but have some idea what the key is.
AI agents call json_query_search_keys to retrieve information from JSON Query MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and searches for keys within JSON data structures without creating, modifying, or deleting any data. It is a passive information retrieval operation with no side effects, fitting squarely within the Read category. The low severity reflects that even if misused by an agent, it can only expose information already present in the JSON file, posing minimal risk.
From the tool's definition Tool description states 'Search for keys in a JSON file' and 'extract information from large JSON data'. The server is designed for 'querying' and 'searching' without any mention of modification, deletion, or execution capabilities.
Documented attack patterns abuse exactly the kind of access json_query_search_keys gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and JSON Query MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for json_query_search_keys:
{
"version": "1",
"default": "deny",
"tools": {
"json_query_search_keys": {}
}
}json_query_search_keys is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search for keys in a JSON file. Use when you do not know the path to a key in a large JSON file, but have some idea what the key is. It is categorised as a Read tool in the JSON Query MCP MCP Server, which means it retrieves data without modifying state.
Register the JSON Query MCP server in PolicyLayer and add a rule for json_query_search_keys: 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 JSON Query MCP. Nothing to install.
json_query_search_keys 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_query_search_keys 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_query_search_keys. 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_query_search_keys is provided by the JSON Query MCP server (mgraczyk/json-query-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from JSON Query MCP, 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.
3 JSON Query MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.