subgraph_vespa_lock_history

THE RISK

Low Risk

Why subgraph_vespa_lock_history needs a policy

This tool retrieves historical data about lock events for a given address. It is a pure read/query operation with no side effects, modifications, or financial transactions involved.

From the tool's definition Get historical veSPA lock events for an address. Shows when SPA was locked, amounts, and lock durations over time.

Documented attack patterns abuse exactly the kind of access subgraph_vespa_lock_history gives an agent:

POLICY

How to control subgraph_vespa_lock_history

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_lock_history:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "subgraph_vespa_lock_history": {}
  }
}

subgraph_vespa_lock_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Sperax Ecosystem Crypto & DeFI MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Sperax Ecosystem Crypto & DeFI MCP Server tools

Financial api_ultrade_market_cancel_order Cancel open order Financial api_ultrade_market_cancel_orders Cancel multiple open orders Financial binance_us_cancel_oco Cancel an entire OCO order on Binance.US. Cancelling any individual leg will cancel the en Financial binance_us_cancel_order Cancel an active order on Binance.US. Either orderId or origClientOrderId must be provided Financial binance_us_cancel_replace Cancel an existing order and place a new order on the same symbol atomically. This is usef Financial binance_us_cust_cancel_orders_symbol Cancel all active custodial orders for a specific trading pair. ⚠️ REQUIRES CUSTODIAL SOL Financial BinanceCrossMarginCancelAllOrders Cancel all open orders on a symbol in Cross Margin account. Financial BinanceDeliveryCancelBatchOrders Cancel multiple COIN-M Futures orders in batch (max 10).

All 1318 Sperax Ecosystem Crypto & DeFI MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about subgraph_vespa_lock_history

What does the subgraph_vespa_lock_history tool do? +

Get historical veSPA lock events for an address. Shows when SPA was locked, amounts, and lock durations over time. 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.

How do I enforce a policy on subgraph_vespa_lock_history? +

Register the Sperax Ecosystem Crypto & DeFI MCP Server MCP server in PolicyLayer and add a rule for subgraph_vespa_lock_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.

What risk level is subgraph_vespa_lock_history? +

subgraph_vespa_lock_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit subgraph_vespa_lock_history? +

Yes. Add a rate_limit block to the subgraph_vespa_lock_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.

How do I block subgraph_vespa_lock_history completely? +

Set action: deny in the PolicyLayer policy for subgraph_vespa_lock_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.

What MCP server provides subgraph_vespa_lock_history? +

subgraph_vespa_lock_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.

Enforce policy on every Sperax Ecosystem Crypto & DeFI MCP Server tool call.

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.

CHECK YOUR STACK →