get_credit_usage
Check credit balance, usage history, and cost breakdown. Shows remaining credits, usage by model/endpoint, and top cost drivers. Useful for cost optimization, budget monitoring, and reviewing whether activities are cost-effective.
This record as markdown: /tools/com-getfreedomos-freedom-mcp/get-credit-usage.md
What get_credit_usage does on Freedom Mcp
AI agents call get_credit_usage to retrieve information from Freedom Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
period | string | — | Time period for usage breakdown. Default: "month" |
companyId | string | Yes | FreedomOS company id to act within (you must be a member). Required for company-scoped tools. |
breakdown_by | string | — | How to group the usage data. Default: "both" |
Parameters from the server's own tool schema.
Why get_credit_usage is rated Low
This tool retrieves and displays financial data (credit balance, usage history, cost breakdown) for monitoring and analysis purposes only. It has no write, execute, or destructive capability—it does not charge, transfer, or modify credits, nor does it execute code or trigger external operations.
From the tool's definition Tool name 'get_credit_usage' and description 'Check credit balance, usage history, and cost breakdown. Shows remaining credits, usage by model/endpoint, and top cost drivers.' indicate read-only querying of financial metrics without modification or movement…
Attacks that exploit this kind of access
The rule that runs get_credit_usage safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freedom Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_credit_usage, this is the rule to start with:
get_credit_usage 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 Freedom Mcp, apply this rule, and every get_credit_usage call is checked against it from then on.
Questions about get_credit_usage
Check credit balance, usage history, and cost breakdown. Shows remaining credits, usage by model/endpoint, and top cost drivers. Useful for cost optimization, budget monitoring, and reviewing whether activities are cost-effective. It is categorised as a Read tool in the Freedom Mcp MCP Server, which means it retrieves data without modifying state.
get_credit_usage accepts 3 parameters: period, companyId, breakdown_by. Required: companyId. The full parameter table on this page comes from the server's own tool schema.
Register the Freedom MCP server in PolicyLayer and add a rule for get_credit_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 Freedom Mcp. Nothing to install.
get_credit_usage 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_credit_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.
Set action: deny in the PolicyLayer policy for get_credit_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.
get_credit_usage is provided by the Freedom MCP server (https://twuluxmoognlwtmaoqgo.supabase.co/functions/v1/freedom-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freedom, and thousands of servers like it.
This server
Across the catalogue