Low Risk

get_last_metric

Get the most recent ML metric.

How to control get_last_metric ↓

AI agents call get_last_metric 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.

Low Risk

This tool retrieves or queries existing data (ML metrics) without modifying, deleting, or executing anything. It has no side effects and poses minimal risk even if misused by an AI agent, as it only returns information rather than changing system state.

From the tool's definition Tool name 'get_last_metric' and description 'Get the most recent ML metric' indicate a retrieval operation with no side effects. The verb 'Get' and the read-only nature of fetching existing metric data confirm this is a Read operation.

Documented attack patterns abuse exactly the kind of access get_last_metric 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_last_metric:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_last_metric": {}
  }
}

get_last_metric is read-only, so it stays allowed — but 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.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_last_metric tool do? +

Get the most recent ML metric. 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_last_metric? +

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

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

Can I rate-limit get_last_metric? +

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

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

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