export_map_devices
Export device location data as a GPX file to the user's Nextcloud /Maps folder.
This record as markdown: /tools/aiquila-nextcloud-mcp-server/export-map-devices.md
What export_map_devices does on AIquila — Nextcloud MCP Server
AI agents use export_map_devices to create or update resources in AIquila — Nextcloud MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AIquila — Nextcloud MCP Server environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
all | boolean | — | If true, filename is not prefixed with 'filtered-' |
end | number | — | End timestamp filter |
begin | number | — | Start timestamp filter |
deviceIdList | array | Yes | Device IDs to export |
Parameters from the server's own tool schema.
Why export_map_devices is rated Medium
This tool creates and writes a new file (GPX format) to persistent storage in Nextcloud. While file creation is reversible (can be deleted), the act of writing location data to a file is a Write operation.
From the tool's definition The tool description states it will 'export device location data as a GPX file to the user's Nextcloud /Maps folder', indicating creation of a new file in the user's storage.
Attacks that exploit this kind of access
The rule that runs export_map_devices 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 export_map_devices, this is the rule to start with:
export_map_devices stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 export_map_devices call is checked against it from then on.
Questions about export_map_devices
Export device location data as a GPX file to the user's Nextcloud /Maps folder. It is categorised as a Write tool in the AIquila — Nextcloud MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
export_map_devices accepts 4 parameters: all, end, begin, deviceIdList. Required: deviceIdList. 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 export_map_devices: 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.
export_map_devices is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the export_map_devices 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 export_map_devices. 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.
export_map_devices 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