Get the schema information for a specific table.
AI agents call get_table_schema to retrieve information from Postgres MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves database schema metadata (column names, types, constraints, etc.) for inspection purposes. It performs a read-only operation with no side effects, reversible modifications, code execution, data deletion, or financial impact. The blast radius of misuse is minimal—an agent could learn the database structure but cannot modify or access actual data rows through this tool alone.
From the tool's definition Tool name 'get_table_schema' and description 'Get the schema information for a specific table' indicate retrieval of metadata with no modification or deletion of data.
Attacks that exploit this kind of access
Get the schema information for a specific table. It is categorised as a Read tool in the Postgres MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Postgres MCP Server MCP server in PolicyLayer and add a rule for get_table_schema: 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 Server. Nothing to install.
get_table_schema 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_schema 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_schema. 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_schema is provided by the Postgres MCP Server MCP server (wongjingping/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 →