audit_get_cycle_digest

Return a compact read-only digest for one audit cycle, with optional final summary payload.

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/audit-get-cycle-digest.md

What audit_get_cycle_digest does on Codex CCXT MCP

AI agents call audit_get_cycle_digest 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 audit_get_cycle_digest is rated Low

The tool explicitly declares 'read-only' semantics, indicating it retrieves or queries audit cycle information without triggering any state changes, deletions, or financial operations. This aligns with the Read category definition: retrieves or queries data with no side effects.

From the tool's definition audit_get_cycle_digest is described as a 'read-only digest' with no side effects—it retrieves and returns audit cycle data without modification, deletion, or execution of external operations.

Questions about audit_get_cycle_digest

What does the audit_get_cycle_digest tool do? +

Return a compact read-only digest for one audit cycle, with optional final summary payload. 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 audit_get_cycle_digest? +

Register the Codex CCXT MCP server in PolicyLayer and add a rule for audit_get_cycle_digest: 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 audit_get_cycle_digest? +

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

Can I rate-limit audit_get_cycle_digest? +

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

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

audit_get_cycle_digest 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.