Screen a Hedera account against on-chain risk signals including transaction
AI agents call identity_check_sanctions to retrieve information from Hedera Toolbox without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries on-chain data to assess sanctions risk for a given account. It retrieves and analyzes existing blockchain information without creating, modifying, executing operations, or deleting anything. The financial context (HBAR micropayments) is incidental cost, not the tool's function.
From the tool's definition The tool name 'identity_check_sanctions' and description 'Screen a Hedera account against on-chain risk signals including transaction' indicate a lookup/screening operation.
Attacks that exploit this kind of access
Screen a Hedera account against on-chain risk signals including transaction. It is categorised as a Read tool in the Hedera Toolbox MCP Server, which means it retrieves data without modifying state.
Register the Hedera Toolbox MCP server in PolicyLayer and add a rule for identity_check_sanctions: 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 Hedera Toolbox. Nothing to install.
identity_check_sanctions 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 identity_check_sanctions 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 identity_check_sanctions. 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.
identity_check_sanctions is provided by the Hedera Toolbox MCP server (mountainmystic/hederatoolbox). 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 →