find-related-tables
AI agents call find-related-tables to retrieve information from Supabase MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the empty description, the tool name strongly indicates a schema discovery/introspection function, which retrieves metadata about database relationships. This has no side effects on data. The confidence is reduced due to the missing description, but the name's semantics and the server's stated purpose (data analysis via SQL, schema exposure) support Read classification.
From the tool's definition Tool name 'find-related-tables' suggests discovery or lookup of related tables in a database schema. The server context indicates it 'exposes table schemas as resources' and provides 'tools for data analysis.' No description provided, but the naming pattern…
Attacks that exploit this kind of access
find-related-tables. It is categorised as a Read tool in the Supabase MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Supabase MCP Server MCP server in PolicyLayer and add a rule for find-related-tables: 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 Supabase MCP Server. Nothing to install.
find-related-tables 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-related-tables 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-related-tables. 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-related-tables is provided by the Supabase MCP Server MCP server (stefanraath3/mcp-supabase). 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 →