Cast a vote in the current debate. Complements the judge: votes are tallied
AI agents use cast_vote to create or update resources in Claude Team MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Team MCP environment.
This tool modifies debate state by recording a vote, which is a reversible write operation. It does not read external data (Read), execute arbitrary code (Execute), delete information (Destructive), or handle financial transactions (Financial). The impact is limited to internal debate mechanics of a team coordination system, warranting low severity.
From the tool's definition Tool name 'cast_vote' and description 'Cast a vote in the current debate. Complements the judge: votes are tallied' indicate creation/modification of voting state within a debate coordination system.
Attacks that exploit this kind of access
Cast a vote in the current debate. Complements the judge: votes are tallied. It is categorised as a Write tool in the Claude Team MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Team 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 Claude Team MCP. 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 Claude Team MCP server (lakshan12367/mcp). 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 →