export_map_route
Export a route or track as a GPX file to the user's Nextcloud /Maps folder.
This record as markdown: /tools/aiquila-nextcloud-mcp-server/export-map-route.md
What export_map_route does on AIquila — Nextcloud MCP Server
AI agents use export_map_route 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 |
|---|---|---|---|
name | string | Yes | Route name (used as filename) |
type | string | Yes | GPX structure type: 'route' (<rte>) or 'track' (<trk>) |
coords | array | Yes | Ordered list of coordinates |
myMapId | number | — | Target map ID (defaults to /Maps folder) |
totDist | number | — | Total distance (for metadata) |
totTime | number | — | Total time (for metadata) |
Parameters from the server's own tool schema.
Why export_map_route is rated Medium
This tool creates or writes a new GPX file to the user's Nextcloud folder (/Maps). This is a Write operation—it creates data reversibly and can be undone by deleting the exported file. There is no destructive action, code execution, financial impact, or irreversible operation. The blast radius is minimal as it only affects the user's own storage space.
From the tool's definition Tool description states 'Export a route or track as a GPX file to the user's Nextcloud /Maps folder,' which creates a new file in the user's storage.
Attacks that exploit this kind of access
The rule that runs export_map_route 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_route, this is the rule to start with:
export_map_route 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_route call is checked against it from then on.
Questions about export_map_route
Export a route or track 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_route accepts 6 parameters: name, type, coords, myMapId, totDist, totTime. Required: name, type, coords. 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_route: 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_route 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_route 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_route. 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_route 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