Deposits funds into the user
AI agents use citrex_deposit 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.
Depositing funds on a blockchain protocol is a financial operation that moves actual assets. In a DeFi context, this commits user funds to a smart contract, which constitutes a financial obligation/movement. Misuse could result in funds being deposited into unintended addresses or protocols. Severity is high due to the irreversible nature of blockchain transactions and the direct financial impact.
From the tool's definition 'Deposits funds into the user' — the word 'deposit' in the context of a DeFi/blockchain server (Citrex protocol) implies moving real on-chain assets (tokens/funds) into a protocol position.
Attacks that exploit this kind of access
Deposits funds into 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_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 SEI MCP Server V2. Nothing to install.
citrex_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 citrex_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 citrex_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.
citrex_deposit 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.
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 →