add_map_device_point

Log a GPS location point for a device. The device is auto-created by user_agent if it doesn't exist.

SERVERAIquila — Nextcloud MCP Server SOURCEelgorro/aiquila

Medium RISK CLASS

Category Write

Parameters 72 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiquila-nextcloud-mcp-server/add-map-device-point.md

WHAT IT DOES

What add_map_device_point does on AIquila — Nextcloud MCP Server

AI agents use add_map_device_point 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
`lat`	number	Yes	Latitude
`lng`	number	Yes	Longitude
`battery`	number	—	Battery level percentage
`accuracy`	number	—	GPS accuracy in meters
`altitude`	number	—	Altitude in meters
`timestamp`	number	—	Unix timestamp (defaults to now)
`user_agent`	string	—	Device identifier (defaults to HTTP User-Agent)

Parameters from the server's own tool schema.

RISK

Why add_map_device_point is rated Medium

This tool creates or modifies location tracking records in a Nextcloud system. While not destructive (data can be corrected/deleted) and not immediately financial, it persistently writes GPS data which could reveal user locations or device movements.

From the tool's definition Tool name 'add_map_device_point' and description 'Log a GPS location point for a device' indicates creation/insertion of tracking data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

add_map_device_point Rate-limited

add_map_device_point 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_map_device_point": {
      "limits": [
        {
          "counter": "add_map_device_point_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect AIquila — Nextcloud MCP Server, apply this rule, and every add_map_device_point call is checked against it from then on.

FAQ

Questions about add_map_device_point

What does the add_map_device_point tool do? +

Log a GPS location point for a device. The device is auto-created by user_agent if it doesn't exist. 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.

What parameters does add_map_device_point accept? +

add_map_device_point accepts 7 parameters: lat, lng, battery, accuracy, altitude, timestamp, user_agent. Required: lat, lng. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on add_map_device_point? +

Register the AIquila — Nextcloud MCP Server MCP server in PolicyLayer and add a rule for add_map_device_point: 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.

What risk level is add_map_device_point? +

add_map_device_point is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_map_device_point? +

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

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

add_map_device_point 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.

KEEP EXPLORING

More on AIquila — Nextcloud MCP Server, and thousands of servers like it.

This server

All 301 AIquila — Nextcloud MCP Server tools →

Across the catalogue

add-tag on Kanban MCP Server →kb_add on Persistent Kb → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →