New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

codex_get_normalized_metrics

Get normalized CodingToolMetrics for cross-tool comparison. Combines completions usage and cost data into a standard schema.

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

Questions about codex_get_normalized_metrics

What does the codex_get_normalized_metrics tool do? +

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.

How do I enforce a policy on codex_get_normalized_metrics? +

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.

What risk level is codex_get_normalized_metrics? +

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

Can I rate-limit codex_get_normalized_metrics? +

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.

How do I block codex_get_normalized_metrics completely? +

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.

What MCP server provides codex_get_normalized_metrics? +

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.

// 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 Sage'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.