mysql_temp_table_usage

Analyze MySQL thread pool status and performance metrics.

SERVERMysql SOURCEmukul975/mysql-mcp-server

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/mukul975-mysql-mcp-server/mysql-temp-table-usage.md

WHAT IT DOES

What mysql_temp_table_usage does on Mysql

AI agents call mysql_temp_table_usage to retrieve information from Mysql 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_temp_table_usage is rated Low

This tool retrieves and analyzes existing performance metrics and thread pool status. It does not create, modify, delete, execute code, or move money. The word 'Analyze' in the description refers to inspection/reporting of data, not modification. No destructive or state-changing operations are implied.

From the tool's definition Tool name indicates 'usage' analysis; description states 'Analyze MySQL thread pool status and performance metrics' — both suggest querying/monitoring operations with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mysql_temp_table_usage safely

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

mysql_temp_table_usage Allowed

mysql_temp_table_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_temp_table_usage": {}
  }
}

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

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

FAQ

Questions about mysql_temp_table_usage

What does the mysql_temp_table_usage tool do? +

Analyze MySQL thread pool status and performance metrics. It is categorised as a Read tool in the Mysql MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on mysql_temp_table_usage? +

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

What risk level is mysql_temp_table_usage? +

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

Can I rate-limit mysql_temp_table_usage? +

Yes. Add a rate_limit block to the mysql_temp_table_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_temp_table_usage completely? +

Set action: deny in the PolicyLayer policy for mysql_temp_table_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_temp_table_usage? +

mysql_temp_table_usage is provided by the Mysql MCP server (mukul975/mysql-mcp-server). 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 233 Mysql tools →

Across the catalogue

The MCP Attack Database →

Guides

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