Generate CREATE TABLE statement for an existing table
AI agents call get_table_ddl 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 retrieves Data Definition Language (DDL) metadata for an existing table without modifying, executing operations, deleting data, or committing financial actions. It is a pure read operation that queries and returns schema information. The sibling destructive tools (drop_table, delete_data) and write tools (create_table, alter_table) confirm this is distinct—get_table_ddl has no side effects.
From the tool's definition Tool name 'get_table_ddl' and description 'Generate CREATE TABLE statement for an existing table' indicate retrieval of schema metadata only. The verb 'get' and 'generate' imply read-only operations with no data modification or deletion.
Attacks that exploit this kind of access
Generate CREATE TABLE statement for an existing 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 get_table_ddl: 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_ddl 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_ddl 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_ddl. 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_ddl 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 →