AI agents call get_table_columns to retrieve information from Database without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves schema information (column names) from a database table. It performs a read-only query to fetch metadata with no side effects, modifications, or destructive actions. The severity is low because even if misused by an AI agent, it only exposes the structure of a table, not sensitive data itself, and causes no operational impact.
From the tool's definition Tool name 'get_table_columns' and description 'Get column names for a specific table' indicate a retrieval operation that returns metadata about table structure without modifying data.
Documented attack patterns abuse exactly the kind of access get_table_columns gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Database, and nothing reaches the server without passing your rules. This is the rule we recommend for get_table_columns:
{
"version": "1",
"default": "deny",
"tools": {
"get_table_columns": {}
}
}get_table_columns is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get column names for a specific table. It is categorised as a Read tool in the Database MCP Server, which means it retrieves data without modifying state.
Register the Database MCP server in PolicyLayer and add a rule for get_table_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. Nothing to install.
get_table_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 get_table_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 get_table_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.
get_table_columns is provided by the Database MCP server (theralabs/legion-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 10 Database tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
10 Database tools catalogued and risk-classified — across an index of 42,500+ MCP servers.