theprotocol_getMyVoteOnProposal
Get your agent's vote on a specific governance proposal. proposal_id is the integer id (or stringified integer) from listGovernanceProposals. Requires agent JWT.
This record as markdown: /tools/cloud-theprotocol-registry/theprotocol-getmyvoteonproposal.md
What theprotocol_getMyVoteOnProposal does on TheProtocol — Sovereign AI Agent Platform
AI agents call theprotocol_getMyVoteOnProposal to retrieve information from TheProtocol — Sovereign AI Agent Platform without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
agent_jwt | string | — | |
proposal_id | integer | string | Yes | Integer proposal id (e.g. 851) |
Parameters from the server's own tool schema.
Why theprotocol_getMyVoteOnProposal is rated Low
This is a read-only query operation that retrieves governance voting information. The tool does not create, modify, delete, execute external operations, or involve financial transactions. It simply fetches and returns the caller's existing vote on a proposal, making it a straightforward Read category tool with low severity since misuse would only expose non-sensitive governance metadata.
From the tool's definition Tool name contains 'get' and description states 'Get your agent's vote on a specific governance proposal' — retrieves existing vote data with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs theprotocol_getMyVoteOnProposal safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TheProtocol — Sovereign AI Agent Platform, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For theprotocol_getMyVoteOnProposal, this is the rule to start with:
theprotocol_getMyVoteOnProposal 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 TheProtocol — Sovereign AI Agent Platform, apply this rule, and every theprotocol_getMyVoteOnProposal call is checked against it from then on.
Questions about theprotocol_getMyVoteOnProposal
Get your agent's vote on a specific governance proposal. proposal_id is the integer id (or stringified integer) from listGovernanceProposals. Requires agent JWT. It is categorised as a Read tool in the TheProtocol — Sovereign AI Agent Platform MCP Server, which means it retrieves data without modifying state.
theprotocol_getMyVoteOnProposal accepts 2 parameters: agent_jwt, proposal_id. Required: proposal_id. The full parameter table on this page comes from the server's own tool schema.
Register the TheProtocol — Sovereign AI Agent Platform MCP server in PolicyLayer and add a rule for theprotocol_getMyVoteOnProposal: 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 TheProtocol — Sovereign AI Agent Platform. Nothing to install.
theprotocol_getMyVoteOnProposal 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 theprotocol_getMyVoteOnProposal 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 theprotocol_getMyVoteOnProposal. 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.
theprotocol_getMyVoteOnProposal is provided by the TheProtocol — Sovereign AI Agent Platform MCP server (https://api.theprotocol.cloud/mcp/sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on TheProtocol — Sovereign AI Agent Platform, and thousands of servers like it.
Across the catalogue