codex_get_code_interpreter_usage

Get Code Interpreter session usage data for the organization

SERVERSage MCP SOURCEsagemcp/sagemcp

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/sagemcp-sagemcp/codex-get-code-interpreter-usage.md

WHAT IT DOES

What codex_get_code_interpreter_usage does on Sage MCP

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

RISK

Why codex_get_code_interpreter_usage is rated Low

This tool retrieves usage/analytics data about Code Interpreter sessions for an organization. The 'get' verb and lack of any write/execute/delete keywords confirm it is a Read operation.

From the tool's definition Tool name contains 'get' and description states 'Get Code Interpreter session usage data', indicating data retrieval with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs codex_get_code_interpreter_usage safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sage MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For codex_get_code_interpreter_usage, this is the rule to start with:

codex_get_code_interpreter_usage Allowed

codex_get_code_interpreter_usage is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "codex_get_code_interpreter_usage": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sage MCP, apply this rule, and every codex_get_code_interpreter_usage call is checked against it from then on.

FAQ

Questions about codex_get_code_interpreter_usage

What does the codex_get_code_interpreter_usage tool do? +

Get Code Interpreter session usage data for the organization. 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_code_interpreter_usage? +

Register the Sage MCP server in PolicyLayer and add a rule for codex_get_code_interpreter_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_code_interpreter_usage? +

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

Can I rate-limit codex_get_code_interpreter_usage? +

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

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

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

KEEP EXPLORING

More on Sage, and thousands of servers like it.

This server

All 359 Sage tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →