List tables and views visible to the configured PostgreSQL connection.
AI agents call list-tables to retrieve information from Universal Mcp Toolkit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation to enumerate database schema objects. It retrieves information about existing tables and views but does not create, modify, delete, or execute code. The blast radius is minimal as it only exposes metadata that would typically be accessible to any authenticated database user. Classification as Read is appropriate.
From the tool's definition Tool description states 'List tables and views visible to the configured PostgreSQL connection' — a query operation that retrieves metadata without modification or side effects.
Attacks that exploit this kind of access
List tables and views visible to the configured PostgreSQL connection. It is categorised as a Read tool in the Universal Mcp Toolkit MCP Server, which means it retrieves data without modifying state.
Register the Universal Mcp Toolkit MCP server in PolicyLayer and add a rule for list-tables: 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 Universal Mcp Toolkit. Nothing to install.
list-tables 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-tables 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-tables. 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-tables is provided by the Universal Mcp Toolkit MCP server (markgatcha/universal-mcp-toolkit). 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 →