List foreign key relationships. Optionally filter by a specific table.
AI agents call db_relationships to retrieve information from RunContext without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns foreign key relationship metadata from the database schema. It has no side effects, does not modify data, does not execute arbitrary queries or commands, and does not delete or overwrite anything. It is purely informational, similar to other metadata-retrieval tools on this server (db_list_schemas, db_list_tables, db_describe_table).
From the tool's definition Tool description states 'List foreign key relationships' — a read-only operation that retrieves metadata about database structure.
Attacks that exploit this kind of access
List foreign key relationships. Optionally filter by a specific table. It is categorised as a Read tool in the RunContext MCP Server, which means it retrieves data without modifying state.
Register the RunContext MCP server in PolicyLayer and add a rule for db_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 RunContext. Nothing to install.
db_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 db_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 db_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.
db_relationships is provided by the RunContext MCP server (quiet-victory-labs/runcontext). 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 →