Show all indexes of a specific table.
AI agents call get_table_indexes to retrieve information from Mcp Mysql Explorer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves database schema metadata (index information) without executing queries, modifying data, or triggering external operations. It has no side effects and falls squarely into the Read category. Severity is low because index information is typically non-sensitive structural metadata, and misuse would only allow an agent to inspect database organization, not access or modify actual data.
From the tool's definition Tool name 'get_table_indexes' and description 'Show all indexes of a specific table' indicate retrieval of metadata with no modification or execution of queries against data. Returns structural information about table indexes.
Attacks that exploit this kind of access
Show all indexes of a specific table. It is categorised as a Read tool in the Mcp Mysql Explorer MCP Server, which means it retrieves data without modifying state.
Register the Mcp Mysql Explorer MCP server in PolicyLayer and add a rule for get_table_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 Mcp Mysql Explorer. Nothing to install.
get_table_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 get_table_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 get_table_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.
get_table_indexes is provided by the Mcp Mysql Explorer MCP server (xsg22/mcp-mysql-explorer). 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 →