account.analytics.usage
Get your API usage summary — total calls, total cost, cache hit rate, average latency, and unique tools used. Filter by period: 1 day, 7 days, or 30 days. See how efficiently you are using the platform. Free, no charge (APIbase)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/account.analytics.usage.md
What account.analytics.usage does on Apibase
AI agents call account.analytics.usage to retrieve information from Apibase 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 stats: "1d" (24 hours), "7d" (7 days), or "30d" (30 days). Default: "7d" |
Parameters from the server's own tool schema.
Why account.analytics.usage is rated Low
Retrieves account analytics and usage metrics without modifying data or triggering operations.
From the tool's definition Get your API usage summary — total calls, total cost, cache hit rate, average latency, and unique tools used.
Attacks that exploit this kind of access
The rule that runs account.analytics.usage safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For account.analytics.usage, this is the rule to start with:
account.analytics.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 Apibase, apply this rule, and every account.analytics.usage call is checked against it from then on.
Questions about account.analytics.usage
Get your API usage summary — total calls, total cost, cache hit rate, average latency, and unique tools used. Filter by period: 1 day, 7 days, or 30 days. See how efficiently you are using the platform. Free, no charge (APIbase). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
account.analytics.usage accepts 1 parameter: period. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for account.analytics.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 Apibase. Nothing to install.
account.analytics.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 account.analytics.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 account.analytics.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.
account.analytics.usage is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue