Low Risk

get_assets

Get Assets holdings by CryptoAddress

How to control get_assets ↓

What get_assets does on Sperax Ecosystem Crypto & DeFI MCP Server

AI agents call get_assets 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.

Low Risk

Why get_assets needs a policy

This tool retrieves and queries data (asset holdings associated with a cryptocurrency address). It has no side effects, does not execute transactions, does not modify state, and does not move funds. It is purely informational, fitting the 'Read' category. Severity is low because querying public blockchain data poses minimal risk even if misused by an agent.

From the tool's definition Tool name 'get_assets' and description 'Get Assets holdings by CryptoAddress' indicate a retrieval operation that queries asset holdings without modification, deletion, or execution of transactions.

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

How to control get_assets

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_assets": {}
  }
}

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

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_assets

What does the get_assets tool do? +

Get Assets holdings by CryptoAddress. 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 get_assets? +

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

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

Can I rate-limit get_assets? +

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

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

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

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.