evm_address_activity
Where is this address used? One call checks an EVM address on Ethereum, Base, Arbitrum, OP Mainnet, Polygon and BNB Chain: native balance, nonce (transactions sent), contract or EOA, EIP-7702 delegation, code size, and a per-chain active flag plus a summary of chains with activity. Useful before ...
This record as markdown: /tools/com-it-scorptech-x402/evm-address-activity.md
What evm_address_activity does on ScorpTech x402 API
AI agents call evm_address_activity to retrieve information from ScorpTech x402 API without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
chains | array | — | Subset of eth, base, arbitrum, optimism, polygon, bsc (default all six) |
address | string | Yes | EVM address (0x, 20 bytes; EIP-55 checked when mixed case) |
Parameters from the server's own tool schema.
Why evm_address_activity is rated Low
Even though evm_address_activity only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs evm_address_activity safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For evm_address_activity, this is the rule to start with:
evm_address_activity 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 ScorpTech x402 API, apply this rule, and every evm_address_activity call is checked against it from then on.
Questions about evm_address_activity
Where is this address used? One call checks an EVM address on Ethereum, Base, Arbitrum, OP Mainnet, Polygon and BNB Chain: native balance, nonce (transactions sent), contract or EOA, EIP-7702 delegation, code size, and a per-chain active flag plus a summary of chains with activity. Useful before sending funds, for wallet screening and for picking the right chain. Keyless public RPC, read-only. Price: $0.005 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/evm-address-activity. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
evm_address_activity accepts 2 parameters: chains, address. Required: address. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for evm_address_activity: 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 ScorpTech x402 API. Nothing to install.
evm_address_activity 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 evm_address_activity 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 evm_address_activity. 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.
evm_address_activity is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
This server
Across the catalogue