Get MCP Process Metrics.
AI agents call get_mcp_process to retrieve information from Nest Protect MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves process metrics—system telemetry about the MCP server itself—which is a read-only operation with no side effects. It does not create, modify, delete, execute commands, or affect controlled devices. The blast radius of misuse is minimal since an attacker would only gain visibility into process performance data, not control over Nest Protect devices or home safety systems.
From the tool's definition Tool name 'get_mcp_process' and description 'Get MCP Process Metrics' indicate retrieval of process-level monitoring data with no modification or execution capability.
Attacks that exploit this kind of access
Get MCP Process Metrics. It is categorised as a Read tool in the Nest Protect MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Nest Protect MCP Server MCP server in PolicyLayer and add a rule for get_mcp_process: 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 Nest Protect MCP Server. Nothing to install.
get_mcp_process 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_mcp_process 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_mcp_process. 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_mcp_process is provided by the Nest Protect MCP Server MCP server (sandraschi/nest-protect-mcp). 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 →