protect_list_sensors

A read tool on the UniFi Access MCP server.

SERVERUniFi Access MCP SOURCEpypi:unifi-protect-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-sirkirby-unifi-access-mcp/protect-list-sensors.md

WHAT IT DOES

What protect_list_sensors does on UniFi Access MCP

AI agents call protect_list_sensors to retrieve information from UniFi Access MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why protect_list_sensors is rated Low

Despite the empty description reducing confidence slightly, the tool name strongly suggests this retrieves or enumerates sensors (likely door/access sensors in the UniFi Access context) without modifying, deleting, or executing actions. List operations are Read category by default. Confidence is 0.75 due to lack of descriptive text, but the naming convention is unambiguous.

From the tool's definition Tool name 'protect_list_sensors' indicates a list operation that retrieves sensor information. The 'list' verb is a classic Read operation that queries data without side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs protect_list_sensors safely

PolicyLayer is an MCP gateway: it sits between your AI agents and UniFi Access MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For protect_list_sensors, this is the rule to start with:

protect_list_sensors Allowed

protect_list_sensors is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "protect_list_sensors": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect UniFi Access MCP, apply this rule, and every protect_list_sensors call is checked against it from then on.

FAQ

Questions about protect_list_sensors

What does the protect_list_sensors tool do? +

protect_list_sensors is a read tool on the UniFi Access MCP server. It is categorised as a Read tool in the UniFi Access MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on protect_list_sensors? +

Register the UniFi Access MCP server in PolicyLayer and add a rule for protect_list_sensors: 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 UniFi Access MCP. Nothing to install.

What risk level is protect_list_sensors? +

protect_list_sensors is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit protect_list_sensors? +

Yes. Add a rate_limit block to the protect_list_sensors 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.

How do I block protect_list_sensors completely? +

Set action: deny in the PolicyLayer policy for protect_list_sensors. 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.

What MCP server provides protect_list_sensors? +

protect_list_sensors is provided by the UniFi Access MCP server (pypi:unifi-protect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on UniFi Access, and thousands of servers like it.

This server

All 272 UniFi Access tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →