Summarizes local X API usage costs, consumed posts, recent ingest runs, and account-level cost breakdowns from the SQLite archive.
AI agents call archive.billing.summary to retrieve information from X Archive Daemon without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and aggregates historical billing and usage information from local storage for reporting purposes. It does not modify data, execute external commands, delete records, or process payments. The read-only nature of summarizing existing cost metrics places it squarely in the Read category with low severity, as misuse would only expose cost transparency information rather than enable harmful actions.
From the tool's definition Tool name 'archive.billing.summary' and description 'Summarizes local X API usage costs' indicates a read-only retrieval of billing and usage statistics from a local SQLite database.
Attacks that exploit this kind of access
Summarizes local X API usage costs, consumed posts, recent ingest runs, and account-level cost breakdowns from the SQLite archive. It is categorised as a Read tool in the X Archive Daemon MCP Server, which means it retrieves data without modifying state.
Register the X Archive Daemon MCP server in PolicyLayer and add a rule for archive.billing.summary: 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 X Archive Daemon. Nothing to install.
archive.billing.summary 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 archive.billing.summary 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 archive.billing.summary. 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.
archive.billing.summary is provided by the X Archive Daemon MCP server (menesekinci/x-archive-daemon). 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 →