codex_get_normalized_metrics
Get normalized CodingToolMetrics for cross-tool comparison. Combines completions usage and cost data into a standard schema.
This record as markdown: /tools/sagemcp-sagemcp/codex-get-normalized-metrics.md
What codex_get_normalized_metrics does on Sage MCP
AI agents call codex_get_normalized_metrics 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.
Why codex_get_normalized_metrics is rated Low
This tool retrieves and normalizes existing metrics data for comparison purposes. There are no side effects, no data modification, no code execution, and no destructive operations. The action is purely informational/analytical, making it a Read operation with low severity since exposure would only allow viewing aggregated usage and cost metrics.
From the tool's definition Tool description states 'Get normalized CodingToolMetrics' and 'Combines completions usage and cost data into a standard schema' - these are retrieval/read operations that query and aggregate existing metrics data without modification or execution.
Attacks that exploit this kind of access
The rule that runs codex_get_normalized_metrics 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_normalized_metrics, this is the rule to start with:
codex_get_normalized_metrics 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 Sage MCP, apply this rule, and every codex_get_normalized_metrics call is checked against it from then on.
Questions about codex_get_normalized_metrics
Get normalized CodingToolMetrics for cross-tool comparison. Combines completions usage and cost data into a standard schema. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.
Register the Sage MCP server in PolicyLayer and add a rule for codex_get_normalized_metrics: 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.
codex_get_normalized_metrics 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 codex_get_normalized_metrics 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 codex_get_normalized_metrics. 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.
codex_get_normalized_metrics 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.
More on Sage, and thousands of servers like it.
This server
Across the catalogue