Get the column-level schema of a specific table, including column name, data type, max length, and nullability.
AI agents call get_table_schema to retrieve information from Sql Database without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
server | string | Yes | Server hostname (e.g. server1.database.windows.net) |
database | string | Yes | Database name |
table_name | string | Yes | Name of the table to inspect |
Parameters from the server's own tool schema.
This tool only retrieves and inspects metadata about table structure (column names, types, lengths, nullability). It performs no write, delete, execute, or financial operations. It is a passive inspection/query operation with no side effects, fitting the Read category. Severity is low because misuse would only expose schema information, not cause data loss or execute arbitrary code.
From the tool's definition Tool name 'get_table_schema' and description 'Get the column-level schema of a specific table, including column name, data type, max length, and nullability' indicate pure data retrieval with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
Get the column-level schema of a specific table, including column name, data type, max length, and nullability. It is categorised as a Read tool in the Sql Database MCP Server, which means it retrieves data without modifying state.
get_table_schema accepts 3 parameters: server, database, table_name. Required: server, database, table_name. The full parameter table on this page comes from the server's own tool schema.
Register the Sql Database 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 Sql Database. 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 Sql Database MCP server (sql-database-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 →