import_map_devices
Import device location data from a file in Nextcloud storage. Supports GPX, KML, and KMZ.
This record as markdown: /tools/aiquila-nextcloud-mcp-server/import-map-devices.md
What import_map_devices does on AIquila — Nextcloud MCP Server
AI agents use import_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 |
|---|---|---|---|
path | string | Yes | Relative path to the file in Nextcloud storage (e.g. '/Maps/track.gpx') |
Parameters from the server's own tool schema.
Why import_map_devices is rated Medium
The import operation reads external file data and writes/creates records in the map/device system, modifying application state. This is a reversible Write action—the imported data can be deleted or replaced. It does not execute arbitrary code, delete irreversibly, or move funds.
From the tool's definition Tool name 'import_map_devices' combined with description 'Import device location data from a file in Nextcloud storage' indicates creating or populating map device entries from user-provided files.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs import_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 import_map_devices, this is the rule to start with:
import_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 import_map_devices call is checked against it from then on.
Questions about import_map_devices
Import device location data from a file in Nextcloud storage. Supports GPX, KML, and KMZ. 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.
import_map_devices accepts 1 parameter: path. Required: path. 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 import_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.
import_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 import_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 import_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.
import_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