mysql_index_usage

Get index usage statistics from performance_schema.

SERVERMysql Mcp SOURCEoci:docker.io/writenotenow/mysql-mcp:v1.0.0

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-neverinfamous-mysql-mcp/mysql-index-usage.md

WHAT IT DOES

What mysql_index_usage does on Mysql Mcp

AI agents call mysql_index_usage to retrieve information from Mysql Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why mysql_index_usage is rated Low

This tool queries the performance_schema system database to retrieve index usage statistics. It is a read-only operation that retrieves data for analysis purposes without creating, modifying, deleting, or executing any operations. The minimal severity reflects that even if an AI agent misuses this tool, it can only view existing performance metrics, posing no risk to data integrity or system state.

From the tool's definition Tool description states 'Get index usage statistics from performance_schema' — a query operation that retrieves monitoring data with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mysql_index_usage safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mysql Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mysql_index_usage, this is the rule to start with:

mysql_index_usage Allowed

mysql_index_usage is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mysql_index_usage": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mysql Mcp, apply this rule, and every mysql_index_usage call is checked against it from then on.

FAQ

Questions about mysql_index_usage

What does the mysql_index_usage tool do? +

Get index usage statistics from performance_schema. It is categorised as a Read tool in the Mysql Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on mysql_index_usage? +

Register the Mysql MCP server in PolicyLayer and add a rule for mysql_index_usage: 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 Mysql Mcp. Nothing to install.

What risk level is mysql_index_usage? +

mysql_index_usage is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit mysql_index_usage? +

Yes. Add a rate_limit block to the mysql_index_usage 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.

How do I block mysql_index_usage completely? +

Set action: deny in the PolicyLayer policy for mysql_index_usage. 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.

What MCP server provides mysql_index_usage? +

mysql_index_usage is provided by the Mysql MCP server (oci:docker.io/writenotenow/mysql-mcp:v1.0.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mysql, and thousands of servers like it.

This server

All 223 Mysql tools →

Across the catalogue

search_index on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →