Find tables containing columns with specific name patterns
AI agents call find_column to retrieve information from Redshift MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries metadata to locate columns by name pattern, returning information about table structure without modifying, executing code, or deleting data. It is a pure read operation with no side effects. Severity is low because column metadata discovery poses minimal risk even if misused.
From the tool's definition Tool description states 'Find tables containing columns with specific name patterns' — a search/discovery operation. Server is explicitly marked 'Secure, read-only access' with 'schema introspection' as a core capability.
Attacks that exploit this kind of access
Find tables containing columns with specific name patterns. It is categorised as a Read tool in the Redshift MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Redshift MCP Server MCP server in PolicyLayer and add a rule for find_column: 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 Redshift MCP Server. Nothing to install.
find_column 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_column 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_column. 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_column is provided by the Redshift MCP Server MCP server (@davidalbertonogueira/redshift-mcp-server). 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 →