Get a detailed cost report of OpenAI API usage for the current month
AI agents call get_cost_report to retrieve information from Chiro ERP - Issue Pipeline Orchestrator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing cost reporting data without creating, modifying, deleting, or executing any operations. It has read-only semantics. The 'get' verb and 'report' (a passive noun) confirm data retrieval.
From the tool's definition Tool name 'get_cost_report' and description 'Get a detailed cost report of OpenAI API usage for the current month' indicate retrieval of pre-calculated cost data. No parameters mentioned suggest modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Get a detailed cost report of OpenAI API usage for the current month. It is categorised as a Read tool in the Chiro ERP - Issue Pipeline Orchestrator MCP Server, which means it retrieves data without modifying state.
Register the Chiro ERP - Issue Pipeline Orchestrator MCP server in PolicyLayer and add a rule for get_cost_report: 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 Chiro ERP - Issue Pipeline Orchestrator. Nothing to install.
get_cost_report 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 get_cost_report 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 get_cost_report. 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.
get_cost_report is provided by the Chiro ERP - Issue Pipeline Orchestrator MCP server (olwalgeorge2/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →