// MCP TOOL REFERENCE

hydra_contract_call

Call a state-changing method on a NEAR smart contract from the configured account. SAFE: dry=true by default. depositYocto is attached NEAR; gas is in TGas units (default 30 TGas).

ServerNear Hydra
CategoryExecute

How to control hydra_contract_call ↓

WHAT IT DOES

What hydra_contract_call does on Near Hydra

AI agents invoke hydra_contract_call to trigger actions in Near Hydra. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

THE RISK

High Risk

Why hydra_contract_call needs a policy

This tool executes state-changing smart contract calls on the NEAR blockchain, which can have irreversible on-chain effects and involves attaching NEAR tokens (depositYocto). While it defaults to dry=true for safety, when dry=false it executes real transactions. The ability to call arbitrary state-changing contract methods with attached funds makes this Execute/high severity.

From the tool's definition Call a state-changing method on a NEAR smart contract from the configured account. depositYocto is attached NEAR; gas is in TGas units

Documented attack patterns abuse exactly the kind of access hydra_contract_call gives an agent:

POLICY

How to control hydra_contract_call

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_contract_call:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hydra_contract_call": {
      "limits": [
        {
          "counter": "hydra_contract_call_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

hydra_contract_call stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register Near Hydra — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Near Hydra tools

Financial hydra_swap_execute Execute an end-to-end cross-chain swap via NEAR Intents 1Click. Auto-routes the origin sen Financial hydra_swap_submit_deposit Notify 1Click that the deposit transaction has been broadcast. depositAddress comes from a Financial hydra_ensure_gas Top up the derived foreign-chain address with native gas, via a small NEAR Intents 1Click Financial hydra_send_btc Send BTC from a Chain-Signature-derived Bitcoin address. UTXO selection via Mempool API. S Financial hydra_send_evm Send a transaction on an EVM chain from a Chain-Signature-derived address. Supports native Financial hydra_send_ft Send a NEP-141 fungible token from the configured account. Calls ft_transfer with 1 yoctoN Financial hydra_send_near Send native NEAR from the configured account. SAFE BY DEFAULT: dry=true returns the plan w Financial hydra_send_solana Send native SOL from a Chain-Signature-derived Solana address. SAFE: dry=true returns the

All 21 Near Hydra tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Near Hydra → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about hydra_contract_call

What does the hydra_contract_call tool do? +

Call a state-changing method on a NEAR smart contract from the configured account. SAFE: dry=true by default. depositYocto is attached NEAR; gas is in TGas units (default 30 TGas). It is categorised as a Execute tool in the Near Hydra MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on hydra_contract_call? +

Register the Near Hydra MCP server in PolicyLayer and add a rule for hydra_contract_call: 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.

What risk level is hydra_contract_call? +

hydra_contract_call is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit hydra_contract_call? +

Yes. Add a rate_limit block to the hydra_contract_call 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.

How do I block hydra_contract_call completely? +

Set action: deny in the PolicyLayer policy for hydra_contract_call. 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.

What MCP server provides hydra_contract_call? +

hydra_contract_call 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.

Enforce policy on every Near Hydra tool call.

Start from Near Hydra, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

21 Near Hydra tools catalogued and risk-classified — across an index of 43,000+ MCP servers.