Return primary key and foreign key metadata for a table when supported by the ODBC driver.
AI agents call find_relationships to retrieve information from OpenLink MCP Server for ODBC without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves database metadata about table relationships without creating, modifying, deleting, or executing code. It is a schema exploration operation similar to describe_table and describe_table_compact on the same server, consistent with the Read category for data retrieval with no side effects.
From the tool's definition Tool returns 'primary key and foreign key metadata' with no indication of modification, deletion, or execution capabilities. Description explicitly indicates retrieval ('Return') of schema information.
Attacks that exploit this kind of access
Return primary key and foreign key metadata for a table when supported by the ODBC driver. It is categorised as a Read tool in the OpenLink MCP Server for ODBC MCP Server, which means it retrieves data without modifying state.
Register the OpenLink MCP Server for ODBC MCP server in PolicyLayer and add a rule for find_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 OpenLink MCP Server for ODBC. Nothing to install.
find_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 find_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 find_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.
find_relationships is provided by the OpenLink MCP Server for ODBC MCP server (pvsmark/pvs-odbc-mcp). 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 →