check_base_tokens_batch
Pre-screen a WATCHLIST: score up to 20 Base tokens in one call, each with its AVOID / WATCH /
This record as markdown: /tools/0xcnr0-rugsense/check-base-tokens-batch.md
What check_base_tokens_batch does on RugSense
AI agents call check_base_tokens_batch to retrieve information from RugSense without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why check_base_tokens_batch is rated Low
This tool queries/retrieves risk scores and classifications for blockchain tokens—a lookup and analysis function with no side effects. While the server enables trading agents to 'act directly' on outputs, the tool itself only reads/scores data.
From the tool's definition Tool name 'check_base_tokens_batch' and description indicate it 'score[s] up to 20 Base tokens' with risk classifications (AVOID/WATCH/HOT). This retrieves and returns structured scoring/classification data without modifying state or triggering transactions.
Attacks that exploit this kind of access
The rule that runs check_base_tokens_batch safely
PolicyLayer is an MCP gateway: it sits between your AI agents and RugSense, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_base_tokens_batch, this is the rule to start with:
check_base_tokens_batch is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect RugSense, apply this rule, and every check_base_tokens_batch call is checked against it from then on.
Questions about check_base_tokens_batch
Pre-screen a WATCHLIST: score up to 20 Base tokens in one call, each with its AVOID / WATCH /. It is categorised as a Read tool in the RugSense MCP Server, which means it retrieves data without modifying state.
Register the RugSense MCP server in PolicyLayer and add a rule for check_base_tokens_batch: 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 RugSense. Nothing to install.
check_base_tokens_batch is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the check_base_tokens_batch 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.
Set action: deny in the PolicyLayer policy for check_base_tokens_batch. 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.
check_base_tokens_batch is provided by the RugSense MCP server (0xcnr0/rugsense). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on RugSense, and thousands of servers like it.
This server
Across the catalogue