Low Risk

crypto_ratings_bulk

Get Trust Score ratings for all 205 rated tokens in bulk. Returns token_id, name, symbol, trust_score, trust_grade, and risk_level for each. Useful for screening, portfolio construction, or building filtered lists. Example: crypto_ratings_bulk()

Bulk/mass operation — affects multiple targets

Part of the Zarq MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

agentidx/zarq-risk Read Risk 2/5

AI agents call crypto_ratings_bulk to retrieve information from Zarq without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though crypto_ratings_bulk only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

agentidx-zarq-risk.yaml
tools:
  crypto_ratings_bulk:
    rules:
      - action: allow

See the full Zarq policy for all 11 tools.

Tool Name crypto_ratings_bulk
Category Read
MCP Server Zarq MCP Server
Risk Level Low

View all 11 tools →

Agents calling read-class tools like crypto_ratings_bulk have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the crypto_ratings_bulk tool do? +

Get Trust Score ratings for all 205 rated tokens in bulk. Returns token_id, name, symbol, trust_score, trust_grade, and risk_level for each. Useful for screening, portfolio construction, or building filtered lists. Example: crypto_ratings_bulk(). It is categorised as a Read tool in the Zarq MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on crypto_ratings_bulk? +

Add a rule in your Intercept YAML policy under the tools section for crypto_ratings_bulk. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Zarq MCP server.

What risk level is crypto_ratings_bulk? +

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

Can I rate-limit crypto_ratings_bulk? +

Yes. Add a rate_limit block to the crypto_ratings_bulk rule in your Intercept 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 crypto_ratings_bulk completely? +

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

crypto_ratings_bulk is provided by the Zarq MCP server (agentidx/zarq-risk). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Zarq

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.