unifi_recent_events

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/unifi-recent-events.md

What unifi_recent_events does on UniFi Access MCP

AI agents call unifi_recent_events 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 unifi_recent_events is rated Low

The tool appears to retrieve or query recent events from the UniFi Access system. Despite the empty description, the naming convention and analogy to sibling 'access_get_*' tools strongly suggest this is a read-only operation that retrieves event data without side effects. No creation, modification, deletion, execution, or financial operations are indicated.

From the tool's definition Tool name 'unifi_recent_events' and server context indicate retrieval of event logs. Sibling tools include 'access_get_event' and 'access_get_activity_summary', which are clearly Read operations.

Questions about unifi_recent_events

What does the unifi_recent_events tool do? +

unifi_recent_events 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 unifi_recent_events? +

Register the UniFi Access MCP server in PolicyLayer and add a rule for unifi_recent_events: 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 unifi_recent_events? +

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

Can I rate-limit unifi_recent_events? +

Yes. Add a rate_limit block to the unifi_recent_events 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 unifi_recent_events completely? +

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

unifi_recent_events 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of UniFi Access's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.