AI agents call list_indexes to retrieve information from MSSQL MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates database indexes without altering, executing, or deleting any data or objects. It is a passive inspection capability typical of schema discovery. The low severity reflects minimal blast radius—listing indexes does not expose sensitive data itself and cannot be misused to cause harm to the database.
From the tool's definition Tool name 'list_indexes' and description 'List all indexes in the database' indicate a retrieval/query operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access list_indexes gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MSSQL MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_indexes:
{
"version": "1",
"default": "deny",
"tools": {
"list_indexes": {}
}
}list_indexes is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all indexes in the database. It is categorised as a Read tool in the MSSQL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MSSQL MCP Server 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 Server. 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 Server MCP server (jensenloke/mcp-sqlserver-pro). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MSSQL MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
23 MSSQL MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.