citrex_deposit

Deposits funds into the user

SERVERSEI MCP Server V2 SOURCEtestinguser1111111/sei-mcp-server

Critical RISK CLASS

Category Financial

Parameters 00 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/testinguser1111111-sei-mcp-server/citrex-deposit.md

WHAT IT DOES

What citrex_deposit does on SEI MCP Server V2

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.

RISK

Why citrex_deposit is rated Critical

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

RECOMMENDED RULE

The rule that runs citrex_deposit 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_deposit, this is the rule to start with:

citrex_deposit Approval-gated

Any call to citrex_deposit is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "citrex_deposit": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect SEI MCP Server V2, apply this rule, and every citrex_deposit call is checked against it from then on.

FAQ

Questions about citrex_deposit

What does the citrex_deposit tool do? +

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.

How do I enforce a policy on citrex_deposit? +

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.

What risk level is citrex_deposit? +

citrex_deposit is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit citrex_deposit? +

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.

How do I block citrex_deposit completely? +

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.

What MCP server provides citrex_deposit? +

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.

KEEP EXPLORING

More on SEI MCP Server V2, and thousands of servers like it.

This server

All 187 SEI MCP Server V2 tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →