Get detailed CPU metrics including usage, frequency, temperature (if available)
AI agents call get_cpu_metrics to retrieve information from KYC MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns CPU performance data (usage, frequency, temperature). It has no side effects, does not execute arbitrary code or commands, does not modify system state, and poses minimal risk if misused by an AI agent. The worst-case scenario is disclosure of system information, which is a low-severity information disclosure risk.
From the tool's definition Tool name and description indicate 'Get detailed CPU metrics' — a retrieval operation with no parameters suggesting modification or execution of commands. Server is described as 'diagnostics and monitoring' (passive observation).
Attacks that exploit this kind of access
Get detailed CPU metrics including usage, frequency, temperature (if available). It is categorised as a Read tool in the KYC MCP Server MCP Server, which means it retrieves data without modifying state.
Register the KYC MCP Server MCP server in PolicyLayer and add a rule for get_cpu_metrics: 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 KYC MCP Server. Nothing to install.
get_cpu_metrics 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_cpu_metrics 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_cpu_metrics. 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_cpu_metrics is provided by the KYC MCP Server MCP server (vishnurudra-ai/kyc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →