access_get_device

Get detailed device information by ID.

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-get-device.md

WHAT IT DOES

What access_get_device does on UniFi Access MCP

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

This tool retrieves device information without side effects. It is a straightforward data retrieval operation analogous to a GET request in REST APIs. No data is created, modified, deleted, or financial transactions are involved. The function signature (get_device by ID) and description confirm it is purely informational access.

From the tool's definition Tool name and description indicate retrieval: 'Get detailed device information by ID' performs a query operation with no modification or deletion of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

access_get_device Allowed

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

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

FAQ

Questions about access_get_device

What does the access_get_device tool do? +

Get detailed device information by ID. 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_get_device? +

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

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

Can I rate-limit access_get_device? +

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

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

access_get_device 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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