account.analytics.timeseries
Get time-series usage data — calls, cost, cache hits per hour or day over a period. Visualize usage patterns and trends. Choose granularity: hourly (for 1d period) or daily (for 7d/30d). Free, no charge (APIbase)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/account.analytics.timeseries.md
What account.analytics.timeseries does on Apibase
AI agents call account.analytics.timeseries 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: "1d", "7d", or "30d". Default: "7d" |
granularity | string | — | Time bucket granularity: "hour" or "day". Default: "day" |
Parameters from the server's own tool schema.
Why account.analytics.timeseries is rated Low
Retrieves historical analytics data without modifying or executing operations; purely informational query.
From the tool's definition Get time-series usage data — calls, cost, cache hits per hour or day
Attacks that exploit this kind of access
The rule that runs account.analytics.timeseries 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.timeseries, this is the rule to start with:
account.analytics.timeseries 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.timeseries call is checked against it from then on.
Questions about account.analytics.timeseries
Get time-series usage data — calls, cost, cache hits per hour or day over a period. Visualize usage patterns and trends. Choose granularity: hourly (for 1d period) or daily (for 7d/30d). 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.timeseries accepts 2 parameters: period, granularity. 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.timeseries: 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.timeseries 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.timeseries 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.timeseries. 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.timeseries 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