Check whether a contract is deployed and inspect its current on-chain status by known name, script hash, or Neo address
AI agents call get_contract_status to retrieve information from Neo N3 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries the on-chain status of a smart contract. It performs a read-only operation that inspects existing data without creating, modifying, deleting, executing code, or moving assets. The use of 'check' and 'inspect' confirms passive data retrieval. Although it operates on blockchain data, it poses minimal risk as it cannot alter state or trigger financial transactions.
From the tool's definition Tool name 'get_contract_status' and description 'Check whether a contract is deployed and inspect its current on-chain status' indicate retrieval and inspection of blockchain data with no modification or execution of smart contract logic.
Attacks that exploit this kind of access
Check whether a contract is deployed and inspect its current on-chain status by known name, script hash, or Neo address. It is categorised as a Read tool in the Neo N3 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Neo N3 MCP Server MCP server in PolicyLayer and add a rule for get_contract_status: 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 Neo N3 MCP Server. Nothing to install.
get_contract_status 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 get_contract_status 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 get_contract_status. 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.
get_contract_status is provided by the Neo N3 MCP Server MCP server (r3e-network/neo-n3-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →