Search for tables and columns by name using a case-insensitive pattern match. Returns matching tables and columns across all schemas. Useful for finding relevant tables when you
AI agents call searchSchema to retrieve information from Postgresql without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries database metadata (schema information) and returns results without modifying, executing, or deleting anything. It is purely informational, making it a Read category tool. Severity is low because accessing schema metadata poses minimal risk—it does not expose data contents, only table and column names, and cannot be used to cause harm.
From the tool's definition Tool name 'searchSchema' and description 'Search for tables and columns by name using a case-insensitive pattern match. Returns matching tables and columns' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Search for tables and columns by name using a case-insensitive pattern match. Returns matching tables and columns across all schemas. Useful for finding relevant tables when you. It is categorised as a Read tool in the Postgresql MCP Server, which means it retrieves data without modifying state.
Register the Postgresql MCP server in PolicyLayer and add a rule for searchSchema: 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 Postgresql. Nothing to install.
searchSchema 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 searchSchema 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 searchSchema. 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.
searchSchema is provided by the Postgresql MCP server (vnikhilbuddhavarapu/postgresql-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 →