Check the execution status of a 1Click swap by its deposit address.
AI agents call hydra_swap_status 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 read-only lookup of swap execution status. It retrieves state information about an existing swap transaction identified by a deposit address. There are no side effects, no code execution, no data modification, and no financial operations initiated by this tool itself. The blast radius of misuse is minimal—an agent could only learn status information already committed to the blockchain.
From the tool's definition Tool name 'hydra_swap_status' and description 'Check the execution status of a 1Click swap by its deposit address' indicate a query operation that retrieves status information without modifying or executing transactions.
Documented attack patterns abuse exactly the kind of access hydra_swap_status 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_swap_status:
{
"version": "1",
"default": "deny",
"tools": {
"hydra_swap_status": {}
}
}hydra_swap_status 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.
Check the execution status of a 1Click swap by its deposit address. 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_swap_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 Near Hydra. Nothing to install.
hydra_swap_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 hydra_swap_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 hydra_swap_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.
hydra_swap_status 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.