AI agents call find_missing_indexes 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) |
minImpact | number | — | Minimum impact score to include (default: 1000) |
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 database analysis by examining query execution statistics to recommend missing indexes. It reads metadata and execution plan information from the database system views (like sys.dm_db_missing_index_details in SQL Server) but does not execute, modify, delete, or create any actual database objects. The tool is purely informational and has no side effects on the database structure or data.
From the tool's definition Tool name 'find_missing_indexes' and description 'Identify potentially missing indexes based on query execution patterns' indicate a querying/analysis operation.
Attacks that exploit this kind of access
Identify potentially missing indexes based on query execution patterns. It is categorised as a Read tool in the Mssql MCP Server, which means it retrieves data without modifying state.
find_missing_indexes accepts 4 parameters: schema, minImpact, 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 find_missing_indexes: 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.
find_missing_indexes 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 find_missing_indexes 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 find_missing_indexes. 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.
find_missing_indexes 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 →