get_map_device_points
Get GPS location points for a specific device. Supports time filtering and pagination.
This record as markdown: /tools/aiquila-nextcloud-mcp-server/get-map-device-points.md
What get_map_device_points does on AIquila — Nextcloud MCP Server
AI agents call get_map_device_points to retrieve information from AIquila — Nextcloud MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | number | Yes | Device ID |
pruneBefore | number | — | Unix timestamp — only return points after this time |
Parameters from the server's own tool schema.
Why get_map_device_points is rated Low
This tool fetches location data, which is a read operation. However, GPS location tracking data is highly sensitive personal information that could expose device movements, patterns, and whereabouts. The severity is elevated to 'high' due to the sensitivity of the data being accessed, despite the read-only nature of the operation.
From the tool's definition Tool retrieves GPS location points for a device with time filtering and pagination capabilities. The description explicitly indicates data retrieval ('Get') with no modification, deletion, or execution.
Attacks that exploit this kind of access
The rule that runs get_map_device_points safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AIquila — Nextcloud MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_map_device_points, this is the rule to start with:
get_map_device_points 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 AIquila — Nextcloud MCP Server, apply this rule, and every get_map_device_points call is checked against it from then on.
Questions about get_map_device_points
Get GPS location points for a specific device. Supports time filtering and pagination. It is categorised as a Read tool in the AIquila — Nextcloud MCP Server MCP Server, which means it retrieves data without modifying state.
get_map_device_points accepts 2 parameters: id, pruneBefore. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the AIquila — Nextcloud MCP Server MCP server in PolicyLayer and add a rule for get_map_device_points: 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 AIquila — Nextcloud MCP Server. Nothing to install.
get_map_device_points 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 get_map_device_points 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 get_map_device_points. 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.
get_map_device_points is provided by the AIquila — Nextcloud MCP Server MCP server (elgorro/aiquila). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AIquila — Nextcloud MCP Server, and thousands of servers like it.
This server
Across the catalogue