AI agents call analyze_index_usage 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') |
showUnusedOnly | boolean | — | Show only unused indexes (default: false) |
connectionString | string | — | SQL Server connection string (uses default if not provided) |
Parameters from the server's own tool schema.
This tool retrieves and analyzes metadata about database index usage patterns. It queries system views or dynamic management views to display statistics, producing no side effects, data modifications, or destructive operations. It is a pure read operation on database schema/performance metadata, comparable to other sibling analysis tools like analyze_data_distribution and analyze_table_stats.
From the tool's definition The tool description explicitly states it 'Show[s] detailed index usage statistics' and is designed to 'identify unused or underutilized indexes.' The action verb 'Show' combined with the query nature (analyzing statistics) indicates retrieval without…
Attacks that exploit this kind of access
Show detailed index usage statistics to identify unused or underutilized indexes. It is categorised as a Read tool in the Mssql MCP Server, which means it retrieves data without modifying state.
analyze_index_usage accepts 5 parameters: schema, tableName, connectionName, showUnusedOnly, 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_index_usage: 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_index_usage 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_index_usage 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_index_usage. 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_index_usage 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 →