List objects in a schema
AI agents call list_objects to retrieve information from Fluid Postgres without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about database objects (tables, views, functions, etc.) within a schema without creating, modifying, deleting, or executing anything. It is a pure read operation with minimal blast radius if misused—an agent could at worst enumerate database structure, which is informational retrieval only.
From the tool's definition Tool name 'list_objects' and description 'List objects in a schema' indicate a retrieval operation with no modification or execution of code. The verb 'list' is characteristic of Read category tools.
Attacks that exploit this kind of access
List objects in a schema. It is categorised as a Read tool in the Fluid Postgres MCP Server, which means it retrieves data without modifying state.
Register the Fluid Postgres 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 Fluid Postgres. 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 Fluid Postgres MCP server (povesma/fluid-postgres-mcp). 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 →