get_protocol_risk_score

SERVERVaultPilot MCP SOURCEvaultpilot-mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/get-protocol-risk-score.md

WHAT IT DOES

What get_protocol_risk_score does on VaultPilot MCP

AI agents call get_protocol_risk_score to retrieve information from VaultPilot MCP 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
`protocol`	string	Yes

Parameters from the server's own tool schema.

RISK

Why get_protocol_risk_score is rated Low

This is a pure data retrieval and analysis tool. It aggregates publicly available metrics (TVL, audit history, bug-bounty records) to compute a risk assessment. The tool does not execute code, modify state, delete data, or move funds. Even in a financial context (DeFi), reading risk scores and providing analysis is fundamentally a Read operation.

From the tool's definition Tool returns a risk score by querying and aggregating data from DefiLlama and Immunefi—'Return a 0-100 risk score', 'combining TVL size, 30-day TVL trend, contract age, audit count (DefiLlama), and Immunefi bug-bounty status'.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_protocol_risk_score safely

PolicyLayer is an MCP gateway: it sits between your AI agents and VaultPilot MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_protocol_risk_score, this is the rule to start with:

get_protocol_risk_score Allowed

get_protocol_risk_score is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect VaultPilot MCP, apply this rule, and every get_protocol_risk_score call is checked against it from then on.

FAQ

Questions about get_protocol_risk_score

What does the get_protocol_risk_score tool do? +

Return a 0-100 risk score for a DeFi protocol, combining TVL size, 30-day TVL trend, contract age, audit count (DefiLlama), and Immunefi bug-bounty status. Higher = safer. The protocol argument is the DefiLlama slug — works for any chain DefiLlama covers, not just EVM (Solana: marinade-finance, jito, kamino, marginfi, drift; Tron: justlend, sun-io; EVM: aave-v3, uniswap-v3, etc.). Issue #243. SCOPE: this score measures PROTOCOL-LEVEL contract safety, governance, and audit posture (will-the-protocol-rug risk). It does NOT measure individual token upside, price direction, future returns, or 'will this 100x' potential. A high score means the protocol is unlikely to be hacked or exit-scam; it says NOTHING about whether tokens custodied by, traded through, governed by, or related to the protocol will appreciate in price. AGENT BEHAVIOR: this tool surfaces data; it does NOT pick. Use it ONLY for protocol due-diligence ("is Aave V3 safer than Compound V3 to deposit into?"). Do NOT use it to ground speculative token-pick answers — "what coin will 100x", "best memecoin", "should I buy X", "which token will moon". Refuse speculative-pick prompts even when this tool was called; do not present a high score as upside, endorsement, or investment recommendation. Issue #599. It is categorised as a Read tool in the VaultPilot MCP MCP Server, which means it retrieves data without modifying state.

What parameters does get_protocol_risk_score accept? +

get_protocol_risk_score accepts 1 parameter: protocol. Required: protocol. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_protocol_risk_score? +

Register the VaultPilot MCP server in PolicyLayer and add a rule for get_protocol_risk_score: 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 VaultPilot MCP. Nothing to install.

What risk level is get_protocol_risk_score? +

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

Can I rate-limit get_protocol_risk_score? +

Yes. Add a rate_limit block to the get_protocol_risk_score 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 get_protocol_risk_score completely? +

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

get_protocol_risk_score is provided by the VaultPilot MCP server (vaultpilot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on VaultPilot, and thousands of servers like it.

This server

All 189 VaultPilot tools →

Across the catalogue

aiva_get_churn_risk on AIVA MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →