Get detailed information about a table including columns, indexes, and constraints
AI agents call get_table_info to retrieve information from PostgreSQL MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and returns metadata about database structures. It does not execute queries against data, create/modify/delete objects, or trigger external operations. The blast radius of misuse is minimal — an attacker gains only schema visibility, not data access or the ability to modify the database. Classification as Read is appropriate.
From the tool's definition Tool name is 'get_table_info' and description states it retrieves 'detailed information about a table including columns, indexes, and constraints' — purely a query/introspection operation with no modifications or side effects.
Attacks that exploit this kind of access
Get detailed information about a table including columns, indexes, and constraints. It is categorised as a Read tool in the PostgreSQL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PostgreSQL MCP Server MCP server in PolicyLayer and add a rule for get_table_info: 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.
get_table_info 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 get_table_info 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 get_table_info. 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.
get_table_info is provided by the PostgreSQL MCP Server MCP server (reckersai/mcpg). 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 →