Find columns by name pattern across all tables (supports SQL LIKE wildcards: %email%)
AI agents call search_columns to retrieve information from Querybridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries database schema metadata to locate columns matching a name pattern. It retrieves information without creating, modifying, deleting, or executing any data-altering operations. The operation is read-only and has no side effects beyond returning search results.
From the tool's definition Tool name 'search_columns' and description 'Find columns by name pattern across all tables' indicate a search/query operation with no modification capability. The use of SQL LIKE wildcards for pattern matching confirms this is a retrieval operation only.
Attacks that exploit this kind of access
Find columns by name pattern across all tables (supports SQL LIKE wildcards: %email%). It is categorised as a Read tool in the Querybridge MCP Server, which means it retrieves data without modifying state.
Register the Querybridge MCP server in PolicyLayer and add a rule for search_columns: 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 Querybridge. Nothing to install.
search_columns 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_columns 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_columns. 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_columns is provided by the Querybridge MCP server (mahmoudhassanmustafa/querybridge-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 →