pm_manage_voter
Add/remove voter for private market.
This record as markdown: /tools/launch-on-basis-mcp-ts/pm-manage-voter.md
What pm_manage_voter does on Basis MCP Server
AI agents use pm_manage_voter to create or update resources in Basis MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Basis MCP Server environment.
Why pm_manage_voter is rated Medium
The tool modifies access control lists by adding or removing voters from a private market, which is a reversible write operation. While it affects market governance, it does not delete data irreversibly, execute arbitrary code, move funds, or trigger irreversible destruction.
From the tool's definition Tool description states 'Add/remove voter for private market' — these are create/modify operations on voter permissions/access control for market participation.
Attacks that exploit this kind of access
The rule that runs pm_manage_voter 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 pm_manage_voter, this is the rule to start with:
pm_manage_voter 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Basis MCP Server, apply this rule, and every pm_manage_voter call is checked against it from then on.
Questions about pm_manage_voter
Add/remove voter for private market. It is categorised as a Write tool in the Basis MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Basis MCP Server MCP server in PolicyLayer and add a rule for pm_manage_voter: 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.
pm_manage_voter 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 pm_manage_voter 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 pm_manage_voter. 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.
pm_manage_voter 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