vote_on_poll
Cast or change your vote on a poll option. setTo: "yes" to vote yes, "no" to vote no, "maybe" for a tentative yes (only if allowed).
This record as markdown: /tools/aiquila-nextcloud-mcp-server/vote-on-poll.md
What vote_on_poll does on AIquila — Nextcloud MCP Server
AI agents use vote_on_poll 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 |
|---|---|---|---|
setTo | string | Yes | Vote value |
optionId | integer | Yes | Option ID to vote on (from list_poll_options) |
Parameters from the server's own tool schema.
Why vote_on_poll is rated Medium
This tool creates or modifies data (a user's vote on a poll) in a reversible manner—votes can be changed or removed. It does not execute arbitrary code, delete data irreversibly, move money, or trigger external operations. The scope is limited to poll voting state within Nextcloud, making it a straightforward Write operation with low severity given the benign nature of poll voting.
From the tool's definition Tool performs 'Cast or change your vote on a poll option' with setTo parameter accepting 'yes', 'no', or 'maybe' values. This modifies poll voting state in Nextcloud.
Attacks that exploit this kind of access
The rule that runs vote_on_poll 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 vote_on_poll, this is the rule to start with:
vote_on_poll 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 vote_on_poll call is checked against it from then on.
Questions about vote_on_poll
Cast or change your vote on a poll option. setTo: "yes" to vote yes, "no" to vote no, "maybe" for a tentative yes (only if allowed). 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.
vote_on_poll accepts 2 parameters: setTo, optionId. Required: setTo, optionId. 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 vote_on_poll: 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.
vote_on_poll 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 vote_on_poll 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 vote_on_poll. 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.
vote_on_poll 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