Lists archived accounts and their sync state from the local store.
AI agents call archive.accounts.list 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 performs a read-only operation on local archived account metadata. It retrieves information about accounts and their synchronization status from a SQLite database without creating, modifying, or deleting any data.
From the tool's definition Tool name 'archive.accounts.list' and description 'Lists archived accounts and their sync state from the local store' indicate a query operation that retrieves data without modification or side effects.
Attacks that exploit this kind of access
Lists archived accounts and their sync state from 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.list: 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.list 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.list 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.list. 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.list 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 →