pg_object_details

Get detailed metadata for a specific database object (table, view, function, sequence, index).

SERVERPostgreSQL MCP Server SOURCE@neverinfamous/postgres-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-neverinfamous-postgres-mcp/pg-object-details.md

WHAT IT DOES

What pg_object_details does on PostgreSQL MCP Server

AI agents call pg_object_details to retrieve information from PostgreSQL MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why pg_object_details is rated Low

This tool queries and retrieves structural information about database objects without modifying, executing, or deleting anything. It has no side effects and represents a standard metadata inspection capability. The blast radius of misuse is minimal—an attacker could only gain knowledge of database schema, which is a Read-category risk.

From the tool's definition Tool name and description both indicate retrieval of metadata: 'Get detailed metadata for a specific database object'.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pg_object_details safely

PolicyLayer is an MCP gateway: it sits between your AI agents and PostgreSQL MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pg_object_details, this is the rule to start with:

pg_object_details Allowed

pg_object_details is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect PostgreSQL MCP Server, apply this rule, and every pg_object_details call is checked against it from then on.

FAQ

Questions about pg_object_details

What does the pg_object_details tool do? +

Get detailed metadata for a specific database object (table, view, function, sequence, index). It is categorised as a Read tool in the PostgreSQL MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on pg_object_details? +

Register the PostgreSQL MCP Server MCP server in PolicyLayer and add a rule for pg_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 PostgreSQL MCP Server. Nothing to install.

What risk level is pg_object_details? +

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

Can I rate-limit pg_object_details? +

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

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

pg_object_details is provided by the PostgreSQL MCP Server MCP server (@neverinfamous/postgres-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

What pg_object_details does on PostgreSQL MCP Server

Why pg_object_details is rated Low

The rule that runs pg_object_details safely

Questions about pg_object_details

More on PostgreSQL MCP Server, and thousands of servers like it.