Extract and analyze foreign key relationships between tables in the database
AI agents call get_table_relationships to retrieve information from Semantic D1 MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes metadata about database schema relationships (foreign keys) without creating, modifying, or deleting data. It is purely informational, similar to schema inspection tools. The sibling tools (analyze_database_schema, suggest_schema_optimizations, validate_database_schema) reinforce that this server performs read-only analysis and recommendations rather than data manipulation.
From the tool's definition Tool name 'get_table_relationships' and description 'Extract and analyze foreign key relationships' indicate querying/introspection operations. No modification, deletion, or execution of arbitrary operations.
Attacks that exploit this kind of access
Extract and analyze foreign key relationships between tables in the database. It is categorised as a Read tool in the Semantic D1 MCP MCP Server, which means it retrieves data without modifying state.
Register the Semantic D1 MCP server in PolicyLayer and add a rule for get_table_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 Semantic D1 MCP. Nothing to install.
get_table_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_table_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_table_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_table_relationships is provided by the Semantic D1 MCP server (semanticintent/semantic-d1-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_table_relationships is one line of Semantic D1's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →