AI agents call get_relationships to retrieve information from Omnibase without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays metadata about database schema (foreign key relationships) without modifying, executing code, deleting, or moving data. It is purely informational—comparable to INFORMATION_SCHEMA queries or SHOW CONSTRAINTS. No side effects occur from calling this tool.
From the tool's definition Tool description states 'Map foreign key relationships across the database. Returns a list of relationships and a graph showing what each table references and what references it.' The verb 'map' and 'returns' indicate data retrieval with no modification.
Attacks that exploit this kind of access
Map foreign key relationships across the database. Returns a list of relationships and a graph showing what each table references and what references it. Optionally filter to a specific table. It is categorised as a Read tool in the Omnibase MCP Server, which means it retrieves data without modifying state.
Register the Omnibase 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 Omnibase. 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 Omnibase MCP server (omnibase-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 →