update_map_device
Update a device's display color.
This record as markdown: /tools/aiquila-nextcloud-mcp-server/update-map-device.md
What update_map_device does on AIquila — Nextcloud MCP Server
AI agents use update_map_device 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 |
|---|---|---|---|
id | number | Yes | Device ID |
color | string | Yes | New color (e.g. '#ff0000') |
Parameters from the server's own tool schema.
Why update_map_device is rated Medium
This tool creates or modifies data in a reversible manner (changing a display color can be undone by changing it again), which fits the Write category. The modification is cosmetic and non-destructive with minimal blast radius if misused by an AI agent, resulting in low severity.
From the tool's definition Tool name is 'update_map_device' and description states it 'Update[s] a device's display color.' The action modifies an existing device's visual properties (color) reversibly.
Attacks that exploit this kind of access
The rule that runs update_map_device 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 update_map_device, this is the rule to start with:
update_map_device 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 update_map_device call is checked against it from then on.
Questions about update_map_device
Update a device's display color. 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.
update_map_device accepts 2 parameters: id, color. Required: id, color. 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 update_map_device: 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.
update_map_device 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 update_map_device 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 update_map_device. 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.
update_map_device 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