Check API Connection Health.
AI agents call check_api_connectivity 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 performs a connectivity check, which is a read-only diagnostic operation. It queries the API health status but does not create, modify, delete, or execute any operations. The blast radius of misuse is minimal—returning false connection status would not harm the system. No financial, destructive, or execution side effects are possible.
From the tool's definition Tool name 'check_api_connectivity' and description 'Check API Connection Health' indicate a diagnostic query operation that retrieves status information without modifying state or triggering external actions.
Attacks that exploit this kind of access
Check API Connection Health. 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 check_api_connectivity: 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.
check_api_connectivity 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 check_api_connectivity 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 check_api_connectivity. 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.
check_api_connectivity 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 →