mysql_show_engines_status

Show detailed status of all storage engines.

SERVERMcp Windows SOURCEmukul975/mcp-windows-automation

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-mcp-windows-automation/mysql-show-engines-status.md

WHAT IT DOES

What mysql_show_engines_status does on Mcp Windows

AI agents call mysql_show_engines_status to retrieve information from Mcp Windows 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_show_engines_status is rated Low

This tool queries and displays diagnostic information about MySQL storage engines. It performs no modifications, deletions, code execution, or financial operations. It is purely informational retrieval, making it a Read category risk with low severity due to minimal blast radius if misused by an AI agent.

From the tool's definition Tool name 'mysql_show_engines_status' and description 'Show detailed status of all storage engines' indicate a query operation that retrieves information about database storage engine status without modifying or executing operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mysql_show_engines_status safely

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

mysql_show_engines_status Allowed

mysql_show_engines_status 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_show_engines_status": {}
  }
}

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

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

FAQ

Questions about mysql_show_engines_status

What does the mysql_show_engines_status tool do? +

Show detailed status of all storage engines. It is categorised as a Read tool in the Mcp Windows MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on mysql_show_engines_status? +

Register the Mcp Windows MCP server in PolicyLayer and add a rule for mysql_show_engines_status: 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_show_engines_status? +

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

Can I rate-limit mysql_show_engines_status? +

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

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

mysql_show_engines_status 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.

KEEP EXPLORING

More on Mcp Windows, and thousands of servers like it.

This server

All 441 Mcp Windows tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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