ccxt_get_config

Return non-secret server configuration, including trading gate and proxy presence.

SERVERCodex CCXT MCP SOURCEoci:ghcr.io/lucyfox199818-collab/ccxt-mcp:0.1.0
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/io-github-lucyfox199818-collab-ccxt-mcp/ccxt-get-config.md

What ccxt_get_config does on Codex CCXT MCP

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

Why ccxt_get_config is rated Low

This tool retrieves configuration information without modifying, executing, or deleting anything. The description explicitly states it returns 'non-secret' data, meaning sensitive credentials are excluded. Configuration inspection is a read operation with minimal blast radius—useful for auditing system state but incapable of causing side effects or harm.

From the tool's definition Tool name 'ccxt_get_config' and description 'Return non-secret server configuration' indicates retrieval of configuration data with explicit exclusion of secrets. The verb 'Return' and qualifier 'non-secret' confirm read-only information access.

Questions about ccxt_get_config

What does the ccxt_get_config tool do? +

Return non-secret server configuration, including trading gate and proxy presence. It is categorised as a Read tool in the Codex CCXT MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ccxt_get_config? +

Register the Codex CCXT MCP server in PolicyLayer and add a rule for ccxt_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 Codex CCXT MCP. Nothing to install.

What risk level is ccxt_get_config? +

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

Can I rate-limit ccxt_get_config? +

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

Set action: deny in the PolicyLayer policy for ccxt_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 ccxt_get_config? +

ccxt_get_config is provided by the Codex CCXT MCP server (oci:ghcr.io/lucyfox199818-collab/ccxt-mcp:0.1.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Codex CCXT, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Codex CCXT's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.