send_poll
AI agents use send_poll to create or update resources in Claudegram — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claudegram environment.
send_poll creates a new poll in a Telegram chat, which is a reversible write operation. It modifies chat state by adding a message artifact. Severity is high because an agent could spam polls, manipulate voting behavior, or misuse polls for social engineering in the user's personal Telegram account. Not Execute because it doesn't directly run arbitrary code or scripts—it sends a structured message type.
From the tool's definition Tool name 'send_poll' in a Telegram interaction MCP server, part of a 120-tool suite for 'messaging, media, chat management'. Sibling tools include messaging operations like 'add_contact', 'archive_dialog', and 'click_inline_button'.
Attacks that exploit this kind of access
send_poll. It is categorised as a Write tool in the Claudegram MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claudegram MCP server in PolicyLayer and add a rule for send_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 Claudegram. Nothing to install.
send_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 send_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 send_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.
send_poll is provided by the Claudegram MCP server (sanjar-x/claudegram). 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 →