Analyze table inheritance hierarchies and partitioning structures.
AI agents call check_table_inheritance to retrieve information from Postgres without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs analysis and inspection of table structures (inheritance and partitioning) which is a read-only operation. It retrieves and examines schema information but does not execute code, modify data, delete resources, or commit financial transactions. The word 'Analyze' and 'check' further confirms it is an informational/diagnostic tool. No side effects or data mutations are implied.
From the tool's definition Tool name 'check_table_inheritance' and description 'Analyze table inheritance hierarchies and partitioning structures' indicate a diagnostic/analytical operation that queries database metadata without modifying data.
Documented attack patterns abuse exactly the kind of access check_table_inheritance gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Postgres, and nothing reaches the server without passing your rules. This is the rule we recommend for check_table_inheritance:
{
"version": "1",
"default": "deny",
"tools": {
"check_table_inheritance": {}
}
}check_table_inheritance is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Analyze table inheritance hierarchies and partitioning structures. It is categorised as a Read tool in the Postgres MCP Server, which means it retrieves data without modifying state.
Register the Postgres MCP server in PolicyLayer and add a rule for check_table_inheritance: 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. Nothing to install.
check_table_inheritance 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 check_table_inheritance 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 check_table_inheritance. 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.
check_table_inheritance is provided by the Postgres MCP server (mukul975/postgres-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Postgres, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
239 Postgres tools catalogued and risk-classified — across an index of 43,000+ MCP servers.