Verify a compliance record exists on the Hedera blockchain and has not been
AI agents call hcs_verify_record 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 retrieves and verifies data from the Hedera blockchain. Verification operations are inherently read-only — they query immutable ledger state to confirm properties of existing records (existence and integrity). No data is created, modified, deleted, or financial transaction is initiated. The tool has no side effects beyond information retrieval.
From the tool's definition Tool name 'hcs_verify_record' and description 'Verify a compliance record exists on the Hedera blockchain and has not been' indicate a query/verification operation that checks blockchain state without modification.
Attacks that exploit this kind of access
Verify a compliance record exists on the Hedera blockchain and has not been. 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 hcs_verify_record: 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.
hcs_verify_record 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 hcs_verify_record 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 hcs_verify_record. 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.
hcs_verify_record 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 →