AI agents call find_table to retrieve information from Database without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query of database metadata to locate table information. It has no side effects, does not execute arbitrary queries, and does not modify, delete, or create any data. The blast radius of misuse is minimal—an attacker could learn about database structure but cannot access, modify, or destroy data through this tool alone.
From the tool's definition Tool name 'find_table' and description 'Find which database contains a specific table' indicate a search/lookup operation that retrieves metadata without modifying data.
Documented attack patterns abuse exactly the kind of access find_table gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Database, and nothing reaches the server without passing your rules. This is the rule we recommend for find_table:
{
"version": "1",
"default": "deny",
"tools": {
"find_table": {}
}
}find_table is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Find which database contains a specific table. It is categorised as a Read tool in the Database MCP Server, which means it retrieves data without modifying state.
Register the Database MCP server in PolicyLayer and add a rule for find_table: 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 Database. Nothing to install.
find_table 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_table 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_table. 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_table is provided by the Database MCP server (theralabs/legion-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 10 Database tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
10 Database tools catalogued and risk-classified — across an index of 42,500+ MCP servers.