get_interactions

THE RISK

Low Risk

Why get_interactions needs a policy

This tool retrieves wallet interaction history from blockchain data sources. It is a read-only operation analogous to get_logs, get_nft_transfers, and other query tools on this server. There is no execution of code, no data modification, no deletion, and no financial operations.

From the tool's definition Tool name 'get_interactions' and description 'Get wallet interactions with contracts' indicate a query/retrieval operation that reads historical blockchain data without modifying state or triggering transactions.

Documented attack patterns abuse exactly the kind of access get_interactions gives an agent:

POLICY

How to control get_interactions

PolicyLayer is an MCP gateway — it sits between your AI agents and Web3, and nothing reaches the server without passing your rules. This is the rule we recommend for get_interactions:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_interactions": {}
  }
}

get_interactions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Web3 — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Web3 tools

Read get_account_balance Get token balances for a wallet address Read get_blockchain_stats Get blockchain statistics Read get_blocks Get blocks information Read get_currencies Get available currencies Read get_logs Get blockchain logs Read get_nft_holders Get holders of a specific NFT collection Read get_nft_metadata Get metadata for a specific NFT Read get_nft_transfers Get transfer history for NFTs

All 17 Web3 tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_interactions

What does the get_interactions tool do? +

Get wallet interactions with contracts. It is categorised as a Read tool in the Web3 MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_interactions? +

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

What risk level is get_interactions? +

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

Can I rate-limit get_interactions? +

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

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

get_interactions is provided by the Web3 MCP server (tumf/web3-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Web3 tool call.

Start from Web3, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →