Search for tables by name pattern
AI agents call search_tables to retrieve information from Database MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a schema introspection tool that searches and lists tables matching a name pattern. It performs read-only operations on database metadata (catalogs/information schema), with no side effects. The sibling tools (list_tables, list_schemas, describe_table, etc.) reinforce that this server provides metadata browsing capabilities. No data is created, modified, deleted, or executed—only queried.
From the tool's definition Tool name 'search_tables' combined with description 'Search for tables by name pattern' indicates a query operation that retrieves matching table metadata without modifying data.
Attacks that exploit this kind of access
Search for tables by name pattern. It is categorised as a Read tool in the Database MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Database MCP Server MCP server in PolicyLayer and add a rule for search_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 Database MCP Server. Nothing to install.
search_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 search_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 search_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.
search_tables is provided by the Database MCP Server MCP server (zeaozhang/database-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 →