Foreign-key relationships in the database, optionally filtered to one table. Paginated - large schemas should narrow with table or walk pages.
AI agents call list_foreign_keys to retrieve information from Mssql Mcp Node without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
dbKey | string | — | Database key (lowercased). Optional in single-database mode. Call `list_databases` to discover valid keys. |
limit | integer | — | Max rows to return (1..1000). |
table | string | — | |
offset | integer | — | Row offset for pagination. |
Parameters from the server's own tool schema.
This tool retrieves and queries database schema metadata (foreign key relationships) without side effects. It is a read-only operation that returns information about database structure. The pagination note confirms it is a safe listing function. No data is created, modified, deleted, or executed.
From the tool's definition Tool name 'list_foreign_keys' and description 'Foreign-key relationships in the database' indicate retrieval of metadata. No mention of modification, deletion, or execution of operations. Returns schema information only.
Attacks that exploit this kind of access
Foreign-key relationships in the database, optionally filtered to one table. Paginated - large schemas should narrow with table or walk pages. It is categorised as a Read tool in the Mssql Mcp Node MCP Server, which means it retrieves data without modifying state.
list_foreign_keys accepts 4 parameters: dbKey, limit, table, offset. The full parameter table on this page comes from the server's own tool schema.
Register the Mssql Mcp Node MCP server in PolicyLayer and add a rule for list_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 Mssql Mcp Node. Nothing to install.
list_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 list_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 list_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.
list_foreign_keys is provided by the Mssql Mcp Node MCP server (mssql-mcp-node). 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 →