protect_search_detections
A read tool on the UniFi Access MCP server.
This record as markdown: /tools/io-github-sirkirby-unifi-access-mcp/protect-search-detections.md
What protect_search_detections does on UniFi Access MCP
AI agents call protect_search_detections 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.
Why protect_search_detections is rated Low
Without a description, this is inferred from naming conventions. 'Search' operations are generally Read category as they query existing data without modification. However, the medium severity reflects that detections data could be sensitive security information that an AI agent should not broadly access without proper authorization. The confidence is moderated due to the missing description.
From the tool's definition Tool name contains 'search' which typically indicates data retrieval. The 'detections' context suggests querying security event or detection records from a UniFi Access system.
Attacks that exploit this kind of access
The rule that runs protect_search_detections 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_search_detections, this is the rule to start with:
protect_search_detections is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UniFi Access MCP, apply this rule, and every protect_search_detections call is checked against it from then on.
Questions about protect_search_detections
protect_search_detections 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.
Register the UniFi Access MCP server in PolicyLayer and add a rule for protect_search_detections: 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.
protect_search_detections 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 protect_search_detections 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 protect_search_detections. 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.
protect_search_detections 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.
More on UniFi Access, and thousands of servers like it.
This server
Across the catalogue