Get ML engine performance metrics and statistics
AI agents call get_ml_engine_performance to retrieve information from Mcp Windows without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves performance metrics and statistics from an ML engine. It queries existing data without creating, modifying, executing, or deleting anything. The 'get_' verb and passive 'statistics' retrieval confirm this is a read-only operation with minimal security risk.
From the tool's definition Tool name contains 'get_' prefix and description states 'Get ML engine performance metrics and statistics' - both indicate data retrieval with no modification or execution.
Documented attack patterns abuse exactly the kind of access get_ml_engine_performance 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 get_ml_engine_performance:
{
"version": "1",
"default": "deny",
"tools": {
"get_ml_engine_performance": {}
}
}get_ml_engine_performance is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get ML engine performance metrics and statistics. It is categorised as a Read tool in the Mcp Windows MCP Server, which means it retrieves data without modifying state.
Register the Mcp Windows MCP server in PolicyLayer and add a rule for get_ml_engine_performance: 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.
get_ml_engine_performance is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_ml_engine_performance 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 get_ml_engine_performance. 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.
get_ml_engine_performance 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.