update_map_favorite
Update an existing map favorite. Only provided fields are changed.
This record as markdown: /tools/aiquila-nextcloud-mcp-server/update-map-favorite.md
What update_map_favorite does on AIquila — Nextcloud MCP Server
AI agents use update_map_favorite 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 | Favorite ID |
lat | number | — | New latitude |
lng | number | — | New longitude |
name | string | — | New name |
comment | string | — | New comment |
category | string | — | New category |
extensions | string | — | New extensions data |
Parameters from the server's own tool schema.
Why update_map_favorite is rated Medium
The tool modifies an existing map favorite record by updating only the fields provided, which is a classic Write operation. It does not delete data (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or trigger external operations with unpredictable side effects. The blast radius is minimal since the change affects only a user's map favorites and is reversible.
From the tool's definition Tool name contains 'update' and description states 'Update an existing map favorite. Only provided fields are changed.' This is a modification operation that changes data reversibly.
Attacks that exploit this kind of access
The rule that runs update_map_favorite 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_favorite, this is the rule to start with:
update_map_favorite 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_favorite call is checked against it from then on.
Questions about update_map_favorite
Update an existing map favorite. Only provided fields are changed. 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_favorite accepts 7 parameters: id, lat, lng, name, comment, category, extensions. Required: id. 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_favorite: 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_favorite 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_favorite 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_favorite. 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_favorite 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