List Supported Nest Hardware.
AI agents call list_supported_hardware 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 informational data about supported hardware—a passive read operation with no side effects, no code execution, no data modification, and no financial impact. It poses minimal risk if misused by an AI agent, as it only returns reference information.
From the tool's definition Tool name 'list_supported_hardware' and description 'List Supported Nest Hardware' indicate a retrieval operation that queries or enumerates available device types without modifying state or triggering actions.
Attacks that exploit this kind of access
List Supported Nest Hardware. 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 list_supported_hardware: 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.
list_supported_hardware 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 list_supported_hardware 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 list_supported_hardware. 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.
list_supported_hardware 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 →