This record as markdown: /tools/aarna-ai-atv/build-stake-tx.md
What build_stake_tx does on Atv
AI agents invoke build_stake_tx to trigger actions in Atv. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
stakeAmount | string | — | Human-readable vault token amount to stake, e.g. '100' |
userAddress | string | — | EVM address of the staker |
vaultAddress | string | — | Vault contract address |
lockPeriodIndex | string | — | 0-indexed lock period to select from the timelock contract (e.g. '0', '1', '2') |
Parameters from the server's own tool schema.
Why build_stake_tx is rated High
This tool constructs transactions that execute staking operations on Ethereum/Base, locking user assets into smart contracts. While not immediately destructive or moving funds between wallets (Financial category proper), it executes external operations whose consequences are determined by supplied arguments.
From the tool's definition Tool builds transaction steps to stake vault tokens into a timelock contract. The phrase 'build the transaction steps' and 'stake step' indicate this triggers external blockchain operations with financial effects that depend on argument parameters (vault…
Attacks that exploit this kind of access
The rule that runs build_stake_tx safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Atv, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For build_stake_tx, this is the rule to start with:
build_stake_tx 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Atv, apply this rule, and every build_stake_tx call is checked against it from then on.
Questions about build_stake_tx
Build the transaction steps to stake vault tokens into a timelock contract for boosted rewards. Returns an approve step (if needed) and a stake step. It is categorised as a Execute tool in the Atv MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
build_stake_tx accepts 4 parameters: stakeAmount, userAddress, vaultAddress, lockPeriodIndex. The full parameter table on this page comes from the server's own tool schema.
Register the Atv MCP server in PolicyLayer and add a rule for build_stake_tx: 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 Atv. Nothing to install.
build_stake_tx is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the build_stake_tx 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 build_stake_tx. 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.
build_stake_tx is provided by the Atv MCP server (aarna-ai/atv). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Atv, and thousands of servers like it.
This server
Across the catalogue