Retrieves the configuration currently used by the Citrex SDK instance.
AI agents call citrex_get_config to retrieve information from SEI MCP Server V2 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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
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.
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.
citrex_get_config is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
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.
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 →