describe_table
Describe the columns and types of a specific table.
This record as markdown: /tools/aeiyannn-postgree-mcp/describe-table.md
What describe_table does on PostgreSQL MCP Server
AI agents call describe_table to retrieve information from PostgreSQL MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why describe_table is rated Low
This tool only reads and returns table schema information (column names and types). It has no side effects, cannot modify or delete data, and cannot execute arbitrary code. It is clearly a Read operation with minimal security risk. The low severity reflects that schema disclosure has limited blast radius compared to query execution or data modification tools.
From the tool's definition Tool description states it 'Describe the columns and types of a specific table.' This is a schema introspection operation that retrieves metadata about table structure without modifying data or executing arbitrary operations.
Attacks that exploit this kind of access
The rule that runs describe_table safely
PolicyLayer is an MCP gateway: it sits between your AI agents and PostgreSQL MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For describe_table, this is the rule to start with:
describe_table is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect PostgreSQL MCP Server, apply this rule, and every describe_table call is checked against it from then on.
Questions about describe_table
Describe the columns and types of a specific table. 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 describe_table: 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.
describe_table 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 describe_table 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 describe_table. 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.
describe_table is provided by the PostgreSQL MCP Server MCP server (aeiyannn/postgree-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on PostgreSQL MCP Server, and thousands of servers like it.
This server
Across the catalogue