Deposit assets into a Yault ERC-4626 vault for yield generation
AI agents use yault_deposit to commit financial operations through Yault AESP — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Depositing assets into a yield-generating vault constitutes a financial transaction that commits user funds to an external smart contract protocol. While not immediately irreversible in all cases, it represents a significant financial commitment and exposure to smart contract risk. The tool directly moves assets and creates financial obligations, placing it in the Financial category.
From the tool's definition Tool name 'yault_deposit' combined with description 'Deposit assets into a Yault ERC-4626 vault' indicates movement of cryptocurrency assets into a smart contract vault, which commits financial obligations and locks assets.
Attacks that exploit this kind of access
Deposit assets into a Yault ERC-4626 vault for yield generation. It is categorised as a Financial tool in the Yault AESP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Yault AESP MCP server in PolicyLayer and add a rule for yault_deposit: 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 Yault AESP. Nothing to install.
yault_deposit is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the yault_deposit 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 yault_deposit. 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.
yault_deposit is provided by the Yault AESP MCP server (@yault/aesp). 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 →