This record as markdown: /tools/instantkom-mcp-server/update-poll.md
What update_poll does on instantKOM MCP Server
AI agents use update_poll to create or update resources in instantKOM MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your instantKOM MCP Server environment.
Why update_poll is rated Medium
The tool creates or modifies poll data reversibly. While it affects engagement features on the instantKOM platform, it does not delete data (which would be Destructive), execute arbitrary code (Execute), or involve financial transactions (Financial).
From the tool's definition Tool name 'update_poll' and description 'Update an existing poll' indicate modification of existing data without deletion or irreversible changes.
Attacks that exploit this kind of access
The rule that runs update_poll safely
PolicyLayer is an MCP gateway: it sits between your AI agents and instantKOM MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_poll, this is the rule to start with:
update_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 instantKOM MCP Server, apply this rule, and every update_poll call is checked against it from then on.
Questions about update_poll
Update an existing poll. It is categorised as a Write tool in the instantKOM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the instantKOM MCP Server MCP server in PolicyLayer and add a rule for update_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 instantKOM MCP Server. Nothing to install.
update_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 update_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 update_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.
update_poll is provided by the instantKOM MCP Server MCP server (instantkom/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on instantKOM MCP Server, and thousands of servers like it.
This server
Across the catalogue