AI agents call describe_table to retrieve information from Mssql without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
schema | string | — | Schema name (default: dbo) |
tableName | string | Yes | Name of the table to describe |
connectionName | string | — | Named connection to use (e.g., 'production', 'staging') |
connectionString | string | — | SQL Server connection string (uses default if not provided) |
Parameters from the server's own tool schema.
This tool retrieves and queries table schema metadata (columns, data types, constraints) without creating, modifying, deleting, or executing any operations. It is a read-only introspection capability typical of schema exploration, as confirmed by the server description's emphasis on 'schema exploration'. No side effects or state changes occur.
From the tool's definition Tool name 'describe_table' and description states it 'Get[s] detailed schema information for a specific table including columns, data types, and constraints' — purely informational retrieval with no modification or execution of data.
Attacks that exploit this kind of access
Get detailed schema information for a specific table including columns, data types, and constraints. It is categorised as a Read tool in the Mssql MCP Server, which means it retrieves data without modifying state.
describe_table accepts 4 parameters: schema, tableName, connectionName, connectionString. Required: tableName. The full parameter table on this page comes from the server's own tool schema.
Register the Mssql MCP server in PolicyLayer and add a rule for describe_table: 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 Mssql. Nothing to install.
describe_table 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 describe_table 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 describe_table. 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.
describe_table is provided by the Mssql MCP server (mssql-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 →