Show all foreign key relationships for a given table — both outgoing (this table references) and incoming (other tables reference this table).
AI agents call get_foreign_keys to retrieve information from Sql Database without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
server | string | Yes | Server hostname (e.g. server1.database.windows.net) |
database | string | Yes | Database name |
table_name | string | Yes | Name of the table to inspect foreign keys for |
Parameters from the server's own tool schema.
This tool retrieves metadata about database foreign key constraints without executing code, modifying data, or performing destructive operations. It is a passive schema inspection operation similar to sibling tools like 'get_table_schema' and 'list_tables'.
From the tool's definition Tool name 'get_foreign_keys' and description 'Show all foreign key relationships' indicate schema inspection and data retrieval with no modification or execution capability.
Attacks that exploit this kind of access
Show all foreign key relationships for a given table — both outgoing (this table references) and incoming (other tables reference this table). It is categorised as a Read tool in the Sql Database MCP Server, which means it retrieves data without modifying state.
get_foreign_keys accepts 3 parameters: server, database, table_name. Required: server, database, table_name. The full parameter table on this page comes from the server's own tool schema.
Register the Sql Database MCP server in PolicyLayer and add a rule for 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 Sql Database. Nothing to install.
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 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 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.
get_foreign_keys is provided by the Sql Database MCP server (sql-database-mcp-server). 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 →