Low Risk

lion_token_risk_indicators

Call before any swap or token interaction. Returns transparent risk_score 0-1 + itemized flags (contract verification, mint/freeze/fee/blacklist, holder concentration, liquidity age, etc.) for Base/Ethereum/Solana. Mechanical only. Keyless x402. Use with credits for high-volume agents. Essential ...

Risk signalsHandles credentials or secrets (token)

Part of the LION - keyless data for AI agents: CPG, enrichment, social (attested) server.

lion_token_risk_indicators is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE LION - KEYLESS DATA FOR AI AGENTS: CPG, ENRICHMENT, SOCIAL (ATTESTED) →

Free to start. No card required.

AI agents call lion_token_risk_indicators to retrieve information from LION - keyless data for AI agents: CPG, enrichment, social (attested) 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 lion_token_risk_indicators 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.

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

See the full LION - keyless data for AI agents: CPG, enrichment, social (attested) policy for all 20 tools.

Get this rule live on your own LION - keyless data for AI agents: CPG, enrichment, social (attested) server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY LION - KEYLESS DATA FOR AI AGENTS: CPG, ENRICHMENT, SOCIAL (ATTESTED) →

View all 20 tools →

These attack patterns abuse exactly the kind of access lion_token_risk_indicators gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so lion_token_risk_indicators only ever does what you allow.

SECURE LION - KEYLESS DATA FOR AI AGENTS: CPG, ENRICHMENT, SOCIAL (ATTESTED) →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the lion_token_risk_indicators tool do? +

Call before any swap or token interaction. Returns transparent risk_score 0-1 + itemized flags (contract verification, mint/freeze/fee/blacklist, holder concentration, liquidity age, etc.) for Base/Ethereum/Solana. Mechanical only. Keyless x402. Use with credits for high-volume agents. Essential for autonomous trading / wallet agents. [x402 paid tool: GET /api/x402/token-risk-indicators-json?src=mcp returns the 402 challenge with the canonical payTo; price 0.01 USDC on Base eip155:8453.]. It is categorised as a Read tool in the LION - keyless data for AI agents: CPG, enrichment, social (attested) MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on lion_token_risk_indicators? +

Register the LION - keyless data for AI agents: CPG, enrichment, social (attested) MCP server in PolicyLayer and add a rule for lion_token_risk_indicators: 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 LION - keyless data for AI agents: CPG, enrichment, social (attested). Nothing to install.

What risk level is lion_token_risk_indicators? +

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

Can I rate-limit lion_token_risk_indicators? +

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

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

lion_token_risk_indicators is provided by the LION - keyless data for AI agents: CPG, enrichment, social (attested) MCP server (https://lionx402.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every LION - keyless data for AI agents: CPG, enrichment, social (attested) tool call.

Deterministic rules across all 20 LION - keyless data for AI agents: CPG, enrichment, social (attested) tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.