get_last_metric
Get the most recent ML metric.
This record as markdown: /tools/mukul975-mcp-windows-automation/get-last-metric.md
What get_last_metric does on Mcp Windows
AI agents call get_last_metric 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.
Why get_last_metric is rated Low
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.
Attacks that exploit this kind of access
The rule that runs get_last_metric 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_last_metric, this is the rule to start with:
get_last_metric is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Windows, apply this rule, and every get_last_metric call is checked against it from then on.
Questions about get_last_metric
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.
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.
get_last_metric 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_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.
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.
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.
More on Mcp Windows, and thousands of servers like it.
This server
Across the catalogue