citrex_get_config

Retrieves the configuration currently used by the Citrex SDK instance.

SERVERSEI MCP Server V2 SOURCEtestinguser1111111/sei-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What citrex_get_config does on SEI MCP Server V2

AI agents call citrex_get_config to retrieve information from SEI MCP Server V2 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why citrex_get_config is rated Low

This tool only retrieves existing configuration data without side effects. It is a simple read operation that queries the current state of a Citrex SDK instance. While the server enables DeFi and blockchain operations, this specific tool is limited to data retrieval of configuration settings, posing minimal security risk.

From the tool's definition Tool name contains 'get' and description states 'Retrieves the configuration'. No modification, deletion, or execution of external operations occurs. Returns current state of SDK configuration.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

citrex_get_config Allowed

citrex_get_config is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "citrex_get_config": {}
  }
}

ALLOW ONLY 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_get_config call is checked against it from then on.

FAQ

Questions about citrex_get_config

What does the citrex_get_config tool do? +

Retrieves the configuration currently used by the Citrex SDK instance. It is categorised as a Read tool in the SEI MCP Server V2 MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on citrex_get_config? +

Register the SEI MCP Server V2 MCP server in PolicyLayer and add a rule for citrex_get_config: 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_get_config? +

citrex_get_config is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit citrex_get_config? +

Yes. Add a rate_limit block to the citrex_get_config 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_get_config completely? +

Set action: deny in the PolicyLayer policy for citrex_get_config. 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_get_config? +

citrex_get_config 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 →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →