This record as markdown: /tools/io-github-1lystore-mcp-server/1ly-withdraw.md
What 1ly_withdraw does on 1ly
AI agents use 1ly_withdraw to commit financial operations through 1ly, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why 1ly_withdraw is rated Critical
Withdrawals commit financial obligations and transfer value (USDC, $1LY tokens, or other funds) from a user account to an external address. This is an irreversible movement of money that could result in complete loss of available balance if misused by an AI agent (e.g., withdrawing to an attacker-controlled wallet). Financial category takes precedence over Execute due to the explicit movement of funds.
From the tool's definition Tool description states it 'Request a withdrawal of your available balance to a Solana wallet', which moves funds/money from the platform to an external wallet address.
Attacks that exploit this kind of access
The rule that runs 1ly_withdraw safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 1ly, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For 1ly_withdraw, this is the rule to start with:
Any call to 1ly_withdraw is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect 1ly, apply this rule, and every 1ly_withdraw call is checked against it from then on.
Questions about 1ly_withdraw
Request a withdrawal of your available balance to a Solana wallet (requires ONELY_API_KEY). It is categorised as a Financial tool in the 1ly MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the 1ly MCP server in PolicyLayer and add a rule for 1ly_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 1ly. Nothing to install.
1ly_withdraw 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 1ly_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 1ly_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.
1ly_withdraw is provided by the 1ly MCP server (@1ly/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 1ly, and thousands of servers like it.
Across the catalogue