whitelist_wallets · Basis MCP Server MCP: Risk & Policy

WHAT IT DOES

What whitelist_wallets does on Basis MCP Server

AI agents use whitelist_wallets to create or update resources in Basis MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Basis MCP Server environment.

WHY IT NEEDS A POLICY

Why whitelist_wallets needs a policy

This tool modifies token whitelisting rules, which changes who can interact with a frozen token. While not destructive (the change can be undone) or directly moving funds, it is a write operation that alters the state and permissions of blockchain assets. The severity is high because misconfiguration could lock legitimate users out of their assets or grant unintended access, creating financial harm.

From the tool's definition Tool name 'whitelist_wallets' and description 'Add wallets to frozen token' indicate modification of token access control lists. The action is reversible (wallets can be removed from whitelists) but affects financial permissions on blockchain assets.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

whitelist_wallets Rate-limited

whitelist_wallets stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "whitelist_wallets": {
      "limits": [
        {
          "counter": "whitelist_wallets_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Basis MCP Server, so you can run agents against it safely.

FAQ

Questions about whitelist_wallets

What does the whitelist_wallets tool do? +

Add wallets to frozen token. It is categorised as a Write tool in the Basis MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on whitelist_wallets? +

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

What risk level is whitelist_wallets? +

whitelist_wallets is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit whitelist_wallets? +

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

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

whitelist_wallets is provided by the Basis MCP Server MCP server (launch-on-basis/mcp-ts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.