Get the native-asset balance of an address on a foreign chain.
AI agents call hydra_address_balance to retrieve information from Near Hydra 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 read operation to fetch balance information from a blockchain address. It has no side effects, does not execute code or transactions, does not modify data, and does not move funds. The blast radius of misuse is minimal—an attacker could only learn balance information, which is typically public on blockchains anyway. This is a standard Read category tool.
From the tool's definition Tool name 'hydra_address_balance' and description 'Get the native-asset balance of an address on a foreign chain' indicate a query operation that retrieves balance data without modifying or executing any state changes.
Documented attack patterns abuse exactly the kind of access hydra_address_balance gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Near Hydra, and nothing reaches the server without passing your rules. This is the rule we recommend for hydra_address_balance:
{
"version": "1",
"default": "deny",
"tools": {
"hydra_address_balance": {}
}
}hydra_address_balance 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.
Get the native-asset balance of an address on a foreign chain. It is categorised as a Read tool in the Near Hydra MCP Server, which means it retrieves data without modifying state.
Register the Near Hydra MCP server in PolicyLayer and add a rule for hydra_address_balance: 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 Near Hydra. Nothing to install.
hydra_address_balance 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 hydra_address_balance 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 hydra_address_balance. 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.
hydra_address_balance is provided by the Near Hydra MCP server (nikshepsvn/near-hydra). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Near Hydra, 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.
21 Near Hydra tools catalogued and risk-classified — across an index of 43,000+ MCP servers.