citrex_get_tickers
Fetches ticker information for one or all markets from the Citrex protocol.
This record as markdown: /tools/testinguser1111111-sei-mcp-server/citrex-get-tickers.md
What citrex_get_tickers does on SEI MCP Server V2
AI agents call citrex_get_tickers 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.
Why citrex_get_tickers is rated Low
The tool retrieves market ticker data from the Citrex protocol. This is a pure data query with no ability to modify state, execute transactions, delete data, or move funds. The blast radius of misuse is minimal — an agent could only retrieve market information, which is typically public data. No financial transactions, destructive actions, or code execution are involved.
From the tool's definition Tool name includes 'get_tickers' and description states 'Fetches ticker information' — classic read operations that retrieve data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs citrex_get_tickers 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_tickers, this is the rule to start with:
citrex_get_tickers is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect SEI MCP Server V2, apply this rule, and every citrex_get_tickers call is checked against it from then on.
Questions about citrex_get_tickers
Fetches ticker information for one or all markets from the Citrex protocol. 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_tickers: 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_tickers 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_tickers 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_tickers. 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_tickers 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.
This server
Across the catalogue