access_list_events
A read tool on the UniFi Access MCP server.
This record as markdown: /tools/io-github-sirkirby-unifi-access-mcp/access-list-events.md
What access_list_events does on UniFi Access MCP
AI agents call access_list_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 access_list_events is rated Low
UniFi Access manages physical access control (doors, credentials, visitors). An event list could contain security-relevant logs including access attempts, authentication failures, or door activity. While retrieving this data has no direct side effects (making it 'Read' not 'Execute'), the potential sensitivity of access control event logs elevates severity to medium rather than low.
From the tool's definition Tool name 'access_list_events' indicates it lists/retrieves events from a UniFi Access system. The 'list' verb is a read operation. Empty description limits certainty but aligns with sibling tools like 'access_get_event' which are query/retrieval operations.
Attacks that exploit this kind of access
The rule that runs access_list_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_list_events, this is the rule to start with:
access_list_events 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 access_list_events call is checked against it from then on.
Questions about access_list_events
access_list_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.
Register the UniFi Access MCP server in PolicyLayer and add a rule for access_list_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.
access_list_events 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 access_list_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.
Set action: deny in the PolicyLayer policy for access_list_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.
access_list_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.
This server
Across the catalogue