Get foreign key constraints for one table.
AI agents call get_foreign_keys to retrieve information from MSSQL MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves structural metadata (foreign key constraints) from a database table without creating, modifying, deleting, or executing arbitrary code. It is a pure read operation with no side effects. The low severity reflects minimal blast radius—an AI agent misusing this tool would only gain knowledge of table relationships, not access to sensitive data or the ability to alter the schema.
From the tool's definition Tool is named 'get_foreign_keys' and described as retrieving 'foreign key constraints for one table.' The server description emphasizes 'read-only query execution' and the tool performs metadata retrieval with no modification or deletion of data.
Attacks that exploit this kind of access
Get foreign key constraints for one table. It is categorised as a Read tool in the MSSQL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MSSQL MCP Server 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 MSSQL MCP Server. 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 MSSQL MCP Server MCP server (mortada7-11/mssql-mcpo-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 →