List index/statistics metadata for a table when supported by the ODBC driver.
AI agents call list_indexes to retrieve information from OpenLink MCP Server for ODBC without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves read-only metadata about database indexes and statistics for a given table. It has no side effects, does not execute queries against data, and does not modify any state. It is a safe schema exploration operation consistent with other Read operations on this server (e.g., describe_table, get_database_summary).
From the tool's definition Tool name is 'list_indexes' and description states it 'List[s] index/statistics metadata for a table' — purely informational retrieval of database schema metadata with no modification or execution capability.
Attacks that exploit this kind of access
List index/statistics metadata for a table when supported by the ODBC driver. It is categorised as a Read tool in the OpenLink MCP Server for ODBC MCP Server, which means it retrieves data without modifying state.
Register the OpenLink MCP Server for ODBC 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 OpenLink MCP Server for ODBC. 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 OpenLink MCP Server for ODBC MCP server (pvsmark/pvs-odbc-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 →