AI agents call get_relationships to retrieve information from Mssql without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
schema | string | — | Schema name (default: dbo) |
connectionName | string | — | Named connection to use (e.g., 'production', 'staging') |
connectionString | string | — | SQL Server connection string (uses default if not provided) |
Parameters from the server's own tool schema.
This tool queries metadata about foreign key relationships in the database schema. It retrieves information about how tables are related but does not execute code, modify data, delete data, or move money. It is a straightforward read operation on database metadata, similar to INFORMATION_SCHEMA queries. The blast radius of misuse is minimal—an AI agent can only learn about existing relationships, not alter them.
From the tool's definition Tool name 'get_relationships' and description 'Get foreign key relationships between tables' indicate data retrieval with no modification. The verb 'Get' and lack of any destructive, write, or execute language confirm read-only schema introspection.
Attacks that exploit this kind of access
Get foreign key relationships between tables in the database. It is categorised as a Read tool in the Mssql MCP Server, which means it retrieves data without modifying state.
get_relationships accepts 3 parameters: schema, connectionName, connectionString. The full parameter table on this page comes from the server's own tool schema.
Register the Mssql MCP server in PolicyLayer and add a rule for get_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 Mssql. Nothing to install.
get_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_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_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_relationships is provided by the Mssql MCP server (mssql-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 →