List objects in a schema
AI agents call list_objects to retrieve information from Postgres MCP Pro without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or enumerates database objects (tables, views, functions, etc.) within a schema. It is a non-destructive query operation with no side effects—no data is created, modified, deleted, or executed. The blast radius of misuse is minimal, as an agent could at worst enumerate the database structure, which is typically readable metadata. It belongs in the Read category with low severity.
From the tool's definition Tool name 'list_objects' combined with description 'List objects in a schema' indicates a retrieval operation that queries database metadata without modification or execution of arbitrary code.
Attacks that exploit this kind of access
List objects in a schema. It is categorised as a Read tool in the Postgres MCP Pro MCP Server, which means it retrieves data without modifying state.
Register the Postgres MCP Pro MCP server in PolicyLayer and add a rule for list_objects: 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 Pro. Nothing to install.
list_objects 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 list_objects 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 list_objects. 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.
list_objects is provided by the Postgres MCP Pro MCP server (luislopezsanchez/postgres-mcp-server). 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 →