add_date_poll_option
Add a date/time option to a datePoll. Provide startAt as ISO-8601 (e.g. "2026-05-12T14:00:00Z") and durationSeconds (e.g. 3600 for 1 hour).
This record as markdown: /tools/aiquila-nextcloud-mcp-server/add-date-poll-option.md
What add_date_poll_option does on AIquila — Nextcloud MCP Server
AI agents use add_date_poll_option 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 |
|---|---|---|---|
pollId | integer | Yes | Poll ID (must be a datePoll) |
startAt | string | Yes | Start date/time as ISO-8601 (e.g. "2026-05-12T14:00:00Z") |
durationSeconds | integer | Yes | Duration in seconds (0 = single point in time) |
Parameters from the server's own tool schema.
Why add_date_poll_option is rated Medium
This tool creates or adds data to an existing poll (a datePoll), which is a reversible write operation. It does not execute arbitrary code, delete data, or involve financial transactions. The severity is medium because modifying poll options could affect group decision-making or scheduling, but the change is reversible and the blast radius is limited to the specific poll.
From the tool's definition "Add a date/time option to a datePoll" — creates a new poll option, modifying the poll's structure and content.
Attacks that exploit this kind of access
The rule that runs add_date_poll_option 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_date_poll_option, this is the rule to start with:
add_date_poll_option 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 add_date_poll_option call is checked against it from then on.
Questions about add_date_poll_option
Add a date/time option to a datePoll. Provide startAt as ISO-8601 (e.g. "2026-05-12T14:00:00Z") and durationSeconds (e.g. 3600 for 1 hour). 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.
add_date_poll_option accepts 3 parameters: pollId, startAt, durationSeconds. Required: pollId, startAt, durationSeconds. 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 add_date_poll_option: 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.
add_date_poll_option 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 add_date_poll_option 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 add_date_poll_option. 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.
add_date_poll_option 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