Check if an address is a smart contract or an externally owned account (EOA)
AI agents call is_contract to retrieve information from Sperax Ecosystem Crypto & DeFI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple lookup/verification of blockchain address properties. It retrieves information about whether an address holds contract code but does not modify state, execute code, move funds, or delete data. The operation is purely informational with minimal risk even if misused by an agent.
From the tool's definition Tool description states it 'Check[s] if an address is a smart contract or an externally owned account (EOA)' — a read-only query operation with no side effects or data modification.
Documented attack patterns abuse exactly the kind of access is_contract gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sperax Ecosystem Crypto & DeFI MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for is_contract:
{
"version": "1",
"default": "deny",
"tools": {
"is_contract": {}
}
} is_contract is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check if an address is a smart contract or an externally owned account (EOA). It is categorised as a Read tool in the Sperax Ecosystem Crypto & DeFI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sperax Ecosystem Crypto & DeFI MCP Server MCP server in PolicyLayer and add a rule for is_contract: 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 Sperax Ecosystem Crypto & DeFI MCP Server. Nothing to install.
is_contract 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 is_contract 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 is_contract. 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.
is_contract is provided by the Sperax Ecosystem Crypto & DeFI MCP Server MCP server (sperax/sperax-crypto-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Sperax Ecosystem Crypto & DeFI MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
1318 Sperax Ecosystem Crypto & DeFI MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.