Return column definitions (name, data type, nullable, primary key) for a table.
AI agents call get_table_schema to retrieve information from MCP Database Query Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about table structure with no side effects. It falls squarely into the Read category as it only queries and returns schema information. The server context emphasizes read-only operations and SELECT statements only.
From the tool's definition Tool returns column definitions (name, data type, nullable, primary key) for a table. The description explicitly states this is a read-only workflow that enables inspection of table schemas without modification or execution of arbitrary code.
Attacks that exploit this kind of access
Return column definitions (name, data type, nullable, primary key) for a table. It is categorised as a Read tool in the MCP Database Query Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Database Query Server MCP server in PolicyLayer and add a rule for get_table_schema: 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 MCP Database Query Server. Nothing to install.
get_table_schema 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_schema 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_schema. 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_schema is provided by the MCP Database Query Server MCP server (vicus-brits/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 →