Vote on a poll option in a signal post.
AI agents use vote_on_poll to create or update resources in MCP-Networkbot — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP-Networkbot environment.
Voting on a poll is a straightforward data write operation that creates or updates a user's response to a poll question. It is reversible (a user could typically change their vote), has no destructive consequences, does not execute external code or commands, and involves no financial transactions.
From the tool's definition Tool name and description indicate the action is to 'vote on a poll option', which modifies data by recording a vote—a reversible write operation. The verb 'vote' is a form of data creation/modification rather than retrieval, execution, or destruction.
Attacks that exploit this kind of access
Vote on a poll option in a signal post. It is categorised as a Write tool in the MCP-Networkbot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP-Networkbot 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 MCP-Networkbot. 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 MCP-Networkbot MCP server (kunalkhanna2007-sys/networkbot-python). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →