Low Risk

json_select

Extract JSON data with multiple output formats

How to control json_select ↓

What json_select does on Postgres Mcp Legacy

AI agents call json_select 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_select needs a policy

The tool extracts (reads/queries) JSON data and returns it in various formats. 'Extract' implies a read-only retrieval operation with no side effects. Severity is low as it only reads data, though confidence is slightly reduced because the description is minimal and doesn't clarify whether it can query arbitrary JSON paths or has any write capabilities.

From the tool's definition Extract JSON data with multiple output formats

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

How to control json_select

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_select:

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

json_select 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_select

What does the json_select tool do? +

Extract JSON data with multiple output formats. 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_select? +

Register the Postgres Mcp Legacy MCP server in PolicyLayer and add a rule for json_select: 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_select? +

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

Can I rate-limit json_select? +

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

Set action: deny in the PolicyLayer policy for json_select. 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_select? +

json_select 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.