access_get_activity_summary
A read tool on the UniFi Access MCP server.
This record as markdown: /tools/io-github-sirkirby-unifi-access-mcp/access-get-activity-summary.md
What access_get_activity_summary does on UniFi Access MCP
AI agents call access_get_activity_summary 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_get_activity_summary is rated Low
The 'get' prefix strongly suggests this is a read-only operation that retrieves activity summary data from the UniFi Access system. The empty description prevents absolute certainty, but the consistent naming pattern across similar sibling tools and the absence of any write/delete/execute keywords support classifying this as a Read operation with low severity, as it only retrieves information without side effects.
From the tool's definition Tool name contains 'get' and 'summary', indicating data retrieval. No description provided, but naming convention and sibling tools (access_get_credential, access_get_device, access_get_door, access_get_door_status, access_get_event, access_get_health) all…
Attacks that exploit this kind of access
The rule that runs access_get_activity_summary 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_get_activity_summary, this is the rule to start with:
access_get_activity_summary 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_get_activity_summary call is checked against it from then on.
Questions about access_get_activity_summary
access_get_activity_summary 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_get_activity_summary: 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_get_activity_summary 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_get_activity_summary 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_get_activity_summary. 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_get_activity_summary 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