cast_vote
AI agents use cast_vote to create or update resources in Clink MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Clink MCP Server environment.
Casting a vote in a group consensus system creates or modifies voting records and may influence project decisions. This is a Write operation (creates/modifies data reversibly) rather than Read (no state change) or Execute (no external command execution).
From the tool's definition Tool name 'cast_vote' combined with server context showing 'consensus voting' capabilities suggests this tool records or submits a vote, which modifies collaborative voting state. Description is empty, reducing confidence.
Attacks that exploit this kind of access
cast_vote. It is categorised as a Write tool in the Clink MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Clink MCP Server MCP server in PolicyLayer and add a rule for cast_vote: 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 Clink MCP Server. Nothing to install.
cast_vote 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 cast_vote 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 cast_vote. 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.
cast_vote is provided by the Clink MCP Server MCP server (voxos-ai-inc/clink-mcp-server-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 →