Get the current status of Hedera bridge infrastructure including known bridge contracts, wrapped token registry, and bridge health indicators. Costs 0.1 HBAR.
AI agents call bridge_status 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 blockchain state (bridge contracts, wrapped token registry, health metrics) without creating, modifying, executing, or destroying data. While the server operates on live production Hedera and charges HBAR per call, the financial cost is a metering mechanism for API access, not a financial transaction initiated by the tool itself.
From the tool's definition Tool description states 'Get the current status' of bridge infrastructure, contracts, and registry — a retrieval operation with no modification or execution capability.
Attacks that exploit this kind of access
Get the current status of Hedera bridge infrastructure including known bridge contracts, wrapped token registry, and bridge health indicators. Costs 0.1 HBAR. 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 bridge_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 Hedera Toolbox. Nothing to install.
bridge_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 bridge_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 bridge_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.
bridge_status 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 →