Redeem shares from a Yault vault to get underlying assets back
AI agents use yault_redeem to commit financial operations through Yault AESP — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Redeeming shares from a vault is a financial transaction: it burns/exchanges vault shares for underlying crypto assets, effectively withdrawing funds. This falls squarely in the Financial category as it moves monetary value. Misuse by an AI agent could result in unintended liquidation of vault positions, making severity high.
From the tool's definition 'Redeem shares from a Yault vault to get underlying assets back' — redeeming vault shares converts them into underlying assets, committing a financial operation that moves crypto assets
Attacks that exploit this kind of access
Redeem shares from a Yault vault to get underlying assets back. 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_redeem: 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_redeem 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_redeem 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_redeem. 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_redeem 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 →