List all column names for a specific table
AI agents call list_columns 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 retrieves structural information about database tables. It performs no writes, deletions, code execution, or financial operations. The low severity reflects that knowing column names poses minimal risk—it's foundational information readily available through legitimate database access. Confidence is high because the intent is unambiguous from both name and description.
From the tool's definition Tool name 'list_columns' and description 'List all column names for a specific table' indicate a pure retrieval operation that queries schema metadata without modification or side effects.
Attacks that exploit this kind of access
List all column names for a specific table. 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 list_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 Database MCP Server. Nothing to install.
list_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 list_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 list_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.
list_columns 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 →