Set Guard Security Mode.
AI agents use set_security_mode to create or update resources in Nest Protect MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Nest Protect MCP Server environment.
This tool modifies the security mode of smoke/CO detectors. Changing security mode is a reversible write operation (it can be changed back), but the blast radius is high because misconfiguring security mode on life-safety devices (smoke and CO detectors) could suppress alerts or change detection sensitivity, potentially endangering occupants.
From the tool's definition "Set Guard Security Mode" — sets/configures a security mode on Nest Protect devices
Attacks that exploit this kind of access
Set Guard Security Mode. It is categorised as a Write tool in the Nest Protect MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Nest Protect MCP Server MCP server in PolicyLayer and add a rule for set_security_mode: 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.
set_security_mode is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_security_mode 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 set_security_mode. 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.
set_security_mode 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 →