Get the voting power for an address based on staked TNZO.
AI agents call get_voting_power to retrieve information from Tenzro Ledger MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about voting power associated with an address—a query operation with no side effects. It does not create, modify, delete, execute code, move funds, or trigger external state changes. While it operates in a financial/governance context (staking), the tool itself only reads data, making it a Read category risk with low severity.
From the tool's definition Tool name 'get_voting_power' and description 'Get the voting power for an address based on staked TNZO' indicate a data retrieval operation. The verb 'Get' and lack of any modification, deletion, or execution language confirm this is a read-only query.
Attacks that exploit this kind of access
Get the voting power for an address based on staked TNZO. It is categorised as a Read tool in the Tenzro Ledger MCP MCP Server, which means it retrieves data without modifying state.
Register the Tenzro Ledger MCP server in PolicyLayer and add a rule for get_voting_power: 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 Tenzro Ledger MCP. Nothing to install.
get_voting_power 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_voting_power 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_voting_power. 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_voting_power is provided by the Tenzro Ledger MCP server (https://canton-mcp.tenzro.network/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 →