Get historical voting power snapshots for veSPA. Shows how voting power has changed over time due to decay and additional locks.
AI agents call subgraph_vespa_voting_power_history to retrieve information from Sperax Ecosystem Crypto & DeFI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical voting power data from a blockchain subgraph. It performs a read-only query operation that returns information about veSPA (vote-escrowed SPA) voting power over time. There is no capability to modify, delete, execute code, or move funds. The blast radius if misused would be minimal—an agent could only retrieve public historical data already available on the blockchain.
From the tool's definition Tool name contains 'get' and 'history'; description states 'Get historical voting power snapshots' and 'Shows how voting power has changed over time'. These are query operations with no data modification or side effects.
Documented attack patterns abuse exactly the kind of access subgraph_vespa_voting_power_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sperax Ecosystem Crypto & DeFI MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for subgraph_vespa_voting_power_history:
{
"version": "1",
"default": "deny",
"tools": {
"subgraph_vespa_voting_power_history": {}
}
} subgraph_vespa_voting_power_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get historical voting power snapshots for veSPA. Shows how voting power has changed over time due to decay and additional locks. It is categorised as a Read tool in the Sperax Ecosystem Crypto & DeFI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sperax Ecosystem Crypto & DeFI MCP Server MCP server in PolicyLayer and add a rule for subgraph_vespa_voting_power_history: 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 Sperax Ecosystem Crypto & DeFI MCP Server. Nothing to install.
subgraph_vespa_voting_power_history 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 subgraph_vespa_voting_power_history 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 subgraph_vespa_voting_power_history. 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.
subgraph_vespa_voting_power_history is provided by the Sperax Ecosystem Crypto & DeFI MCP Server MCP server (sperax/sperax-crypto-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Sperax Ecosystem Crypto & DeFI MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
1318 Sperax Ecosystem Crypto & DeFI MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.