Get statistics about table size, row count, and disk usage
AI agents call get_table_stats to retrieve information from SQL Server MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves metadata and statistics about tables without executing code, modifying data, or causing side effects. It is a pure read operation that returns informational data about table properties. While it is part of a SQL Server interaction system, this specific tool has no capability to alter state or execute arbitrary operations.
From the tool's definition Tool description states it retrieves 'statistics about table size, row count, and disk usage' with no modification, deletion, or execution capabilities. The verb 'Get' and the passive nature of the statistics indicate read-only querying.
Attacks that exploit this kind of access
Get statistics about table size, row count, and disk usage. It is categorised as a Read tool in the SQL Server MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SQL Server MCP Server MCP server in PolicyLayer and add a rule for get_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 SQL Server MCP Server. Nothing to install.
get_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 get_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 get_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.
get_table_stats is provided by the SQL Server MCP Server MCP server (nebhg/sql-server-mcp). 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 →