get_voter_choice
Get what a voter chose in a dispute round.
This record as markdown: /tools/launch-on-basis-mcp-ts/get-voter-choice.md
What get_voter_choice does on Basis MCP Server
AI agents call get_voter_choice to retrieve information from Basis MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_voter_choice is rated Low
This tool retrieves historical voting information from a dispute resolution mechanism. It performs a data lookup query with no side effects, no code execution, no data modification, and no financial impact. The action is purely informational.
From the tool's definition Tool name 'get_voter_choice' and description 'Get what a voter chose in a dispute round' indicate a retrieval operation that queries voting data without modifying or executing any state changes.
Attacks that exploit this kind of access
The rule that runs get_voter_choice safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Basis MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_voter_choice, this is the rule to start with:
get_voter_choice is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Basis MCP Server, apply this rule, and every get_voter_choice call is checked against it from then on.
Questions about get_voter_choice
Get what a voter chose in a dispute round. It is categorised as a Read tool in the Basis MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Basis MCP Server MCP server in PolicyLayer and add a rule for get_voter_choice: 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 Basis MCP Server. Nothing to install.
get_voter_choice is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_voter_choice 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 get_voter_choice. 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.
get_voter_choice is provided by the Basis MCP Server MCP server (launch-on-basis/mcp-ts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Basis MCP Server, and thousands of servers like it.
This server
Across the catalogue