token_risk_report

SERVERAwesome Base SOURCEB5-Software/awesome-base-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/awesome-base-mcp/token-risk-report.md

WHAT IT DOES

What token_risk_report does on Awesome Base

AI agents call token_risk_report to retrieve information from Awesome Base without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why token_risk_report is rated Low

Tool queries and analyzes contract code for risk signals without modifying or executing anything.

From the tool's definition Returns verified token-contract code plus static honeypot-related signals; evidence for manual review, not safety verdict.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs token_risk_report safely

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

token_risk_report Allowed

token_risk_report 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": {
    "token_risk_report": {}
  }
}

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

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

FAQ

Questions about token_risk_report

What does the token_risk_report tool do? +

Returns verified token-contract code plus static honeypot-related signals such as blacklists, trading gates, adjustable fees, pause controls, minting, delegatecall, and proxy upgradeability. It is evidence for manual review, not a safety verdict. It is categorised as a Read tool in the Awesome Base MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on token_risk_report? +

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

What risk level is token_risk_report? +

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

Can I rate-limit token_risk_report? +

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

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

token_risk_report is provided by the Awesome Base MCP server (B5-Software/awesome-base-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Awesome Base, and thousands of servers like it.

This server

All 44 Awesome Base tools →

Across the catalogue

aiva_get_churn_risk on AIVA MCP Server → The MCP Attack Database →

Guides

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