Get foreign key relationships for a table
AI agents call get_table_relationships 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 queries database schema metadata to understand relationships between tables. It performs no side effects, does not modify data, and does not execute arbitrary operations. It is purely informational, similar to sibling tools like describe_table, get_indexes, and list_tables. The blast radius of misuse is negligible—an AI could only retrieve metadata it could access anyway, and cannot harm data or systems.
From the tool's definition Tool retrieves foreign key relationships for a table—a metadata query operation with no modification, deletion, or execution of code. Description explicitly states 'Get', indicating information retrieval.
Attacks that exploit this kind of access
Get foreign key relationships for a 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_relationships: 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_relationships 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_relationships 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_relationships. 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_relationships is provided by the PostgreSQL MCP Server MCP server (sbfulfil/pg-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 →