AI agents use vote_on_poll to create or update resources in X (Twitter) MCP server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your X (Twitter) MCP server environment.
Voting on a poll creates a new record (the user's vote) in the poll's vote dataset. This is a reversible write operation—the vote can theoretically be changed or removed. It does not delete data irreversibly, execute arbitrary code, trigger financial transactions, or read sensitive information without modification. The '(mocked)' qualifier suggests this is a test/demo implementation, further reducing risk.
From the tool's definition Tool name 'vote_on_poll' and description 'Vote on a poll (mocked)' indicate a creation or modification of poll voting data.
Documented attack patterns abuse exactly the kind of access vote_on_poll gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and X (Twitter) MCP server, and nothing reaches the server without passing your rules. This is the rule we recommend for vote_on_poll:
{
"version": "1",
"default": "deny",
"tools": {
"vote_on_poll": {
"limits": [
{
"counter": "vote_on_poll_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Vote on a poll (mocked). It is categorised as a Write tool in the X (Twitter) MCP server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the X (Twitter) 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 X (Twitter) 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 X (Twitter) MCP server MCP server (rafaljanicki/x-twitter-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 24 X (Twitter) MCP server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
24 X (Twitter) MCP server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.