Reset Configuration to Defaults.
AI agents call reset_mcp_config to permanently remove resources in Nest Protect MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Resetting to defaults overwrites the current configuration state irreversibly. In the context of a safety-critical system managing smoke and carbon monoxide detectors, losing configuration (device mappings, automation rules, credentials) could disable safety monitoring. This is a destructive overwrite operation with high blast radius in a safety-critical environment.
From the tool's definition 'Reset Configuration to Defaults' - resetting configuration is irreversible as it overwrites current settings, which may include OAuth credentials, device configurations, and automation rules for safety-critical smoke/CO detectors
Attacks that exploit this kind of access
Reset Configuration to Defaults. It is categorised as a Destructive tool in the Nest Protect MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Nest Protect MCP Server MCP server in PolicyLayer and add a rule for reset_mcp_config: 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.
reset_mcp_config is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the reset_mcp_config 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 reset_mcp_config. 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.
reset_mcp_config 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 →