Reads one archived account, its sync status, and the coverage scopes already collected in the local store.
AI agents call archive.accounts.get 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 metadata about a single archived account from the local SQLite database. It queries existing data without modification, deletion, or external side effects. The description confirms it is read-only: it merely reports sync status and coverage information. No destructive, financial, or code execution capability is present.
From the tool's definition Tool name contains 'get' and description explicitly states 'Reads one archived account, its sync status, and the coverage scopes already collected in the local store' — retrieval with no side effects.
Attacks that exploit this kind of access
Reads one archived account, its sync status, and the coverage scopes already collected in the local store. 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.accounts.get: 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.accounts.get 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.accounts.get 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.accounts.get. 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.accounts.get 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 →