get_ml_stats

Get ML engine statistics and status

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/get-ml-stats.md

WHAT IT DOES

What get_ml_stats does on Mcp Windows

AI agents call get_ml_stats 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 get_ml_stats is rated Low

This tool retrieves monitoring/diagnostic information about an ML engine's performance and operational state. Querying statistics and status is a passive read operation with no side effects, no code execution, and no data modification. The blast radius of misuse is minimal—an agent could only access information about the ML engine's current state.

From the tool's definition Tool name 'get_ml_stats' with description 'Get ML engine statistics and status' indicates a retrieval operation. The verb 'Get' and the read-only nature of 'statistics and status' queries confirm no data modification or execution occurs.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_ml_stats 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 get_ml_stats, this is the rule to start with:

get_ml_stats Allowed

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

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 get_ml_stats call is checked against it from then on.

FAQ

Questions about get_ml_stats

What does the get_ml_stats tool do? +

Get ML engine statistics and status. 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 get_ml_stats? +

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

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

Can I rate-limit get_ml_stats? +

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

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

get_ml_stats 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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