checkMaliciousAddress
Check if an Ethereum address has been flagged as malicious in the ScamSniffer blacklist database. Returns whether the address is known to be associated with scams or exploits.
This record as markdown: /tools/nanidao-agentek/checkmaliciousaddress.md
What checkMaliciousAddress does on Agentek Eth
AI agents call checkMaliciousAddress to retrieve information from Agentek Eth without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why checkMaliciousAddress is rated Low
This tool retrieves information from a blacklist database without modifying any state, executing code, or causing side effects. It is a pure read operation that queries an external data source (ScamSniffer blacklist) and returns results. While the information could inform security decisions, the tool itself performs no irreversible actions, financial transactions, or code execution.
From the tool's definition Tool description states it 'Check[s] if an Ethereum address has been flagged' and 'Returns whether the address is known to be associated with scams'.
Attacks that exploit this kind of access
The rule that runs checkMaliciousAddress safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Agentek Eth, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For checkMaliciousAddress, this is the rule to start with:
checkMaliciousAddress 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 Agentek Eth, apply this rule, and every checkMaliciousAddress call is checked against it from then on.
Questions about checkMaliciousAddress
Check if an Ethereum address has been flagged as malicious in the ScamSniffer blacklist database. Returns whether the address is known to be associated with scams or exploits. It is categorised as a Read tool in the Agentek Eth MCP Server, which means it retrieves data without modifying state.
Register the Agentek Eth MCP server in PolicyLayer and add a rule for checkMaliciousAddress: 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 Agentek Eth. Nothing to install.
checkMaliciousAddress 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 checkMaliciousAddress 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 checkMaliciousAddress. 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.
checkMaliciousAddress is provided by the Agentek Eth MCP server (nanidao/agentek). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Agentek Eth, and thousands of servers like it.
This server
Across the catalogue