Create a dashboard displaying server health metrics.
AI agents use mysql_server_health_dashboard to create or update resources in Mcp Windows — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Windows environment.
The tool creates a new dashboard (reversible write operation) that displays health metrics. This is a non-destructive modification that visualizes existing data rather than executing commands or deleting resources. The blast radius is limited to dashboard creation and does not affect production data or system state.
From the tool's definition Tool name 'mysql_server_health_dashboard' and description 'Create a dashboard displaying server health metrics' indicate creation of a dashboard artifact.
Documented attack patterns abuse exactly the kind of access mysql_server_health_dashboard 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_server_health_dashboard:
{
"version": "1",
"default": "deny",
"tools": {
"mysql_server_health_dashboard": {
"limits": [
{
"counter": "mysql_server_health_dashboard_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}mysql_server_health_dashboard stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a dashboard displaying server health metrics. It is categorised as a Write tool in the Mcp Windows MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Windows MCP server in PolicyLayer and add a rule for mysql_server_health_dashboard: 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.
mysql_server_health_dashboard is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the mysql_server_health_dashboard 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 mysql_server_health_dashboard. 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.
mysql_server_health_dashboard 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.
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.