Searches archived post text locally using SQLite FTS.
AI agents call archive.posts.search 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.
The tool performs only a read operation on existing archived posts. SQLite FTS is a non-destructive search mechanism. No data is created, modified, deleted, or any external operations triggered. The blast radius of misuse is minimal—an agent could retrieve sensitive post content but cannot alter or harm the archive itself. Classified as Read with low severity.
From the tool's definition Tool searches archived post text using SQLite FTS (Full Text Search) — this is a pure query operation with no side effects. The description explicitly states it searches locally without modification, creation, or deletion of data.
Attacks that exploit this kind of access
Searches archived post text locally using SQLite FTS. 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.posts.search: 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.posts.search 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.posts.search 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.posts.search. 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.posts.search 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 →