Low Risk

codex_get_completions_usage

Get completions usage data for the organization, broken down by time buckets and optional grouping dimensions

How to control codex_get_completions_usage ↓

AI agents call codex_get_completions_usage to retrieve information from Sage MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool queries and retrieves usage metrics/analytics data for an organization. The verb 'get' combined with 'usage data' and the lack of any mutative or destructive language indicates a read-only data retrieval operation. There are no side effects, no code execution, no deletions, and no financial transactions involved. The low severity reflects that exposing usage statistics poses minimal risk of direct harm.

From the tool's definition Tool name contains 'get_' and description states it retrieves ('Get completions usage data') without modification or side effects. Action is 'broken down by time buckets and optional grouping dimensions' indicating data querying/reporting only.

Documented attack patterns abuse exactly the kind of access codex_get_completions_usage gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Sage MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for codex_get_completions_usage:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "codex_get_completions_usage": {}
  }
}

codex_get_completions_usage is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Sage MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the codex_get_completions_usage tool do? +

Get completions usage data for the organization, broken down by time buckets and optional grouping dimensions. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on codex_get_completions_usage? +

Register the Sage MCP server in PolicyLayer and add a rule for codex_get_completions_usage: 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 Sage MCP. Nothing to install.

What risk level is codex_get_completions_usage? +

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

Can I rate-limit codex_get_completions_usage? +

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

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

codex_get_completions_usage is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Sage MCP tool call.

Deterministic rules across all 359 Sage MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

359 Sage MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.