High Risk →

mysql_diagnostics_info

Run comprehensive diagnostics and retrieve aggregated info.

How to control mysql_diagnostics_info ↓

AI agents invoke mysql_diagnostics_info to trigger actions in Mcp Windows. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

High Risk

Although 'diagnostics' may sound informational, the explicit 'Run' verb indicates this tool executes diagnostic operations whose outcomes depend on system state and the diagnostic scope chosen. This is active execution capable of triggering resource-intensive operations, making it Execute rather than Read.

From the tool's definition Tool description states 'Run comprehensive diagnostics and retrieve aggregated info.' The verb 'Run' combined with 'diagnostics' indicates active execution of diagnostic operations, not passive data retrieval.

Documented attack patterns abuse exactly the kind of access mysql_diagnostics_info gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Windows, and nothing reaches the server without passing your rules. This is the rule we recommend for mysql_diagnostics_info:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "mysql_diagnostics_info": {
      "limits": [
        {
          "counter": "mysql_diagnostics_info_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

mysql_diagnostics_info stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mcp Windows — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the mysql_diagnostics_info tool do? +

Run comprehensive diagnostics and retrieve aggregated info. It is categorised as a Execute tool in the Mcp Windows MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on mysql_diagnostics_info? +

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

What risk level is mysql_diagnostics_info? +

mysql_diagnostics_info is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit mysql_diagnostics_info? +

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

Set action: deny in the PolicyLayer policy for mysql_diagnostics_info. 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_diagnostics_info? +

mysql_diagnostics_info is provided by the Mcp Windows MCP server (mukul975/mcp-windows-automation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Windows tool call.

Deterministic rules across all 441 Mcp Windows tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

441 Mcp Windows tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.