get_object_details

THE RISK

Low Risk

Why get_object_details needs a policy

This tool retrieves and displays metadata or schema information about a database object (table, index, function, etc.). It is a read-only query operation with no side effects, no data modification, and no capability to execute code or trigger external operations. The blast radius of misuse is minimal—an agent could only access information that already exists.

From the tool's definition Tool name 'get_object_details' and description 'Show detailed information about a database object' indicate a retrieval operation with no modification, deletion, or execution of arbitrary code.

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

POLICY

How to control get_object_details

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_object_details": {}
  }
}

get_object_details is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Postgres Mcp Legacy — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_object_details

What does the get_object_details tool do? +

Show detailed information about a database object. 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 get_object_details? +

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

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

Can I rate-limit get_object_details? +

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

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

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

CHECK YOUR STACK →