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

WHAT IT DOES

What access_recent_events does on UniFi Access MCP

AI agents call access_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.

RISK

Why access_recent_events is rated Low

Despite the empty description, the name strongly suggests retrieving event records without modification. Event logs in access control systems typically contain sensitive information (entry times, user identities, door access attempts), making this a Read operation with medium severity due to information sensitivity.

From the tool's definition Tool name 'access_recent_events' with empty description; sibling tools show this server manages access control systems.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs access_recent_events 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 access_recent_events, this is the rule to start with:

access_recent_events Allowed

access_recent_events 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": {
    "access_recent_events": {}
  }
}

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 access_recent_events call is checked against it from then on.

FAQ

Questions about access_recent_events

What does the access_recent_events tool do? +

access_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 access_recent_events? +

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

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

Can I rate-limit access_recent_events? +

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

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

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

KEEP EXPLORING

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

This server

All 272 UniFi Access tools →

Across the catalogue

The MCP Attack Database →

Guides

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