citrex_withdraw
Withdraws funds from the user
This record as markdown: /tools/testinguser1111111-sei-mcp-server/citrex-withdraw.md
What citrex_withdraw does on SEI MCP Server V2
AI agents use citrex_withdraw to commit financial operations through SEI MCP Server V2, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why citrex_withdraw is rated Critical
This tool directly transfers or removes funds from a user's account or wallet, constituting a financial operation. The withdrawal of user funds is irreversible once confirmed and represents a commitment of financial resources.
From the tool's definition Tool name 'citrex_withdraw' and description 'Withdraws funds from the user' indicate movement of financial assets from user control.
Attacks that exploit this kind of access
The rule that runs citrex_withdraw safely
PolicyLayer is an MCP gateway: it sits between your AI agents and SEI MCP Server V2, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For citrex_withdraw, this is the rule to start with:
Any call to citrex_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 SEI MCP Server V2, apply this rule, and every citrex_withdraw call is checked against it from then on.
Questions about citrex_withdraw
Withdraws funds from the user. It is categorised as a Financial tool in the SEI MCP Server V2 MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the SEI MCP Server V2 MCP server in PolicyLayer and add a rule for citrex_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 SEI MCP Server V2. Nothing to install.
citrex_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 citrex_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 citrex_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.
citrex_withdraw is provided by the SEI MCP Server V2 MCP server (testinguser1111111/sei-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on SEI MCP Server V2, and thousands of servers like it.
Across the catalogue