Builds an unsigned ERC-4626 redeem transaction calldata to withdraw assets from a MetaMorpho vault on Ethereum, Base, Arbitrum, or Optimism. Call this when an agent needs to exit a MetaMorpho vault position; no approval transaction is required for redemption. Provide vault identifier (address or ...
Part of the Syenite server.
Free to start. No card required.
AI agents call metamorpho.withdraw to retrieve information from Syenite without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though metamorpho.withdraw only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"metamorpho.withdraw": {}
}
}See the full Syenite policy for all 46 tools.
These attack patterns abuse exactly the kind of access metamorpho.withdraw gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Builds an unsigned ERC-4626 redeem transaction calldata to withdraw assets from a MetaMorpho vault on Ethereum, Base, Arbitrum, or Optimism. Call this when an agent needs to exit a MetaMorpho vault position; no approval transaction is required for redemption. Provide vault identifier (address or name fragment), shares as a human-readable amount or the string "max" to redeem the full balance, receiver address to receive underlying assets, and owner address whose shares will be burned. Returns the redeem transaction request; withdrawal is subject to available liquidity in the underlying Morpho Blue markets and Syenite never holds private keys.. It is categorised as a Read tool in the Syenite MCP Server, which means it retrieves data without modifying state.
Register the Syenite MCP server in PolicyLayer and add a rule for metamorpho.withdraw: 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 Syenite. Nothing to install.
metamorpho.withdraw 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 metamorpho.withdraw 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 metamorpho.withdraw. 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.
metamorpho.withdraw is provided by the Syenite MCP server (@syenite/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 46 Syenite tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.