Indexes on a specific table, including columns and uniqueness/primary-key flags. Use to inform JOIN and WHERE choices.
AI agents call list_indexes to retrieve information from Mssql Mcp Node without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
dbKey | string | — | Database key (lowercased). Optional in single-database mode. Call `list_databases` to discover valid keys. |
table | string | Yes |
Parameters from the server's own tool schema.
This tool retrieves database index metadata for a specified table to help with query optimization decisions. It performs a read operation with no side effects, reversals required, or code execution. No data is modified, deleted, or created. The blast radius if misused by an agent is minimal—at worst, an agent learns about available indexes but cannot exploit them to alter data or execute arbitrary code.
From the tool's definition Tool name 'list_indexes' and description 'Indexes on a specific table, including columns and uniqueness/primary-key flags' indicate retrieval of metadata without modification or execution. Verb 'list' confirms read-only operation.
Attacks that exploit this kind of access
Indexes on a specific table, including columns and uniqueness/primary-key flags. Use to inform JOIN and WHERE choices. It is categorised as a Read tool in the Mssql Mcp Node MCP Server, which means it retrieves data without modifying state.
list_indexes accepts 2 parameters: dbKey, table. Required: table. The full parameter table on this page comes from the server's own tool schema.
Register the Mssql Mcp Node MCP server in PolicyLayer and add a rule for list_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 Mcp Node. Nothing to install.
list_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 list_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 list_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.
list_indexes is provided by the Mssql Mcp Node MCP server (mssql-mcp-node). 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 →