Get all foreign key relationships for a table (both referencing and referenced).
AI agents call PostgreSQL_get_foreign_keys 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 retrieves metadata about foreign key constraints in a PostgreSQL database. It has no side effects, does not modify data, and does not execute arbitrary queries or commands. The blast radius of misuse is minimal — an attacker gains only visibility into database schema relationships, which does not compromise data confidentiality significantly beyond schema enumeration. Categorized as Read with low severity.
From the tool's definition Tool name and description indicate it 'Get[s] all foreign key relationships for a table' — a pure data retrieval operation with no modification, deletion, or execution of code.
Documented attack patterns abuse exactly the kind of access PostgreSQL_get_foreign_keys 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 PostgreSQL_get_foreign_keys:
{
"version": "1",
"default": "deny",
"tools": {
"PostgreSQL_get_foreign_keys": {}
}
}PostgreSQL_get_foreign_keys 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.
Get all foreign key relationships for a table (both referencing and referenced). 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 PostgreSQL_get_foreign_keys: 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.
PostgreSQL_get_foreign_keys 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 PostgreSQL_get_foreign_keys 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 PostgreSQL_get_foreign_keys. 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.
PostgreSQL_get_foreign_keys 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.