AI agents call analyze_table_stats 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 | — | Filter by specific table name |
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 performs diagnostic analysis of table metadata and statistics. It reads information about table size, row counts, and last update times without creating, modifying, deleting, or executing any operations. The action is purely informational retrieval, fitting the Read category. Low severity because misuse would only expose database metadata, not cause data loss or enable destructive actions.
From the tool's definition Tool retrieves 'table row counts, size information, and last update statistics' — query and inspection operations with no modification capability.
Attacks that exploit this kind of access
Get table row counts, size information, and last update statistics. It is categorised as a Read tool in the Mssql MCP Server, which means it retrieves data without modifying state.
analyze_table_stats accepts 4 parameters: schema, tableName, connectionName, connectionString. 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 analyze_table_stats: 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.
analyze_table_stats 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 analyze_table_stats 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 analyze_table_stats. 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.
analyze_table_stats 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 →