Get Recent Device Events.
AI agents call get_nest_events 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 historical event data from Nest Protect devices without creating, modifying, deleting, or executing any external operations. While the context involves safety-critical devices, the tool itself is read-only and poses minimal risk—it cannot alter device state or trigger emergency responses. Severity is low because querying events has no side effects and provides only informational data.
From the tool's definition Tool name 'get_nest_events' and description 'Get Recent Device Events' indicate a retrieval operation with no modification or triggering of external actions. The verb 'Get' and the focus on historical events confirm this is a query-only function.
Attacks that exploit this kind of access
Get Recent Device Events. 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_nest_events: 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_nest_events 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_nest_events 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_nest_events. 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_nest_events 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 →