getCreditsUsageHistory

SERVERSocial Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) SOURCEhttps://mcp.xpoz.ai/mcp

Low RISK CLASS

Category Read

Parameters 40 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-xpoz-social-insights/getcreditsusagehistory.md

WHAT IT DOES

What getCreditsUsageHistory does on Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ)

AI agents call getCreditsUsageHistory to retrieve information from Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) 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
`range`	string	—	Time window to analyze. "today" = current day, "7d" = last 7 days, "current_month" = current calendar month, "lifetime" = all time. Default: current_month.
`feedback`	string	—	Optional. Any free-form feedback you want to share — about this tool, other tools, the platform overall, or anything else. Feedback does NOT have to be about th
`_requestId`	string	—
`granularity`	string	—	Bucket size for the time series. "hour" = hourly buckets (best with range=today or 7d), "day" = daily buckets. Default: day.

Parameters from the server's own tool schema.

RISK

Why getCreditsUsageHistory is rated Low

Even though getCreditsUsageHistory only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs getCreditsUsageHistory safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ), and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getCreditsUsageHistory, this is the rule to start with:

getCreditsUsageHistory Allowed

getCreditsUsageHistory is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "getCreditsUsageHistory": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ), apply this rule, and every getCreditsUsageHistory call is checked against it from then on.

FAQ

Questions about getCreditsUsageHistory

What does the getCreditsUsageHistory tool do? +

Get authenticated user's credits and export-rows usage over time, for analyzing usage patterns. Params: range ("today" | "7d" | "current_month" | "lifetime", default current_month), granularity ("hour" | "day", default day). Returns time-series buckets for both credits and exportRows, each with subscriptionUsed, extraUsed, totalUsed, extraPurchased. Use for trend analysis and spotting usage spikes. For current remaining balances, use getAccountDetails instead. Required: authentication. It is categorised as a Read tool in the Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) MCP Server, which means it retrieves data without modifying state.

What parameters does getCreditsUsageHistory accept? +

getCreditsUsageHistory accepts 4 parameters: range, feedback, _requestId, granularity. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on getCreditsUsageHistory? +

Register the Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) MCP server in PolicyLayer and add a rule for getCreditsUsageHistory: 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 Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ). Nothing to install.

What risk level is getCreditsUsageHistory? +

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

Can I rate-limit getCreditsUsageHistory? +

Yes. Add a rate_limit block to the getCreditsUsageHistory 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 getCreditsUsageHistory completely? +

Set action: deny in the PolicyLayer policy for getCreditsUsageHistory. 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 getCreditsUsageHistory? +

getCreditsUsageHistory is provided by the Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) MCP server (https://mcp.xpoz.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ), and thousands of servers like it.

This server

All 52 Social Media Search API — Twitter, Instagram, Reddit, TikTok (XPOZ) tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →