Fetches posts matching an X search query and stores them in the local archive.
AI agents use ingest.search.backfill to create or update resources in X Archive Daemon — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your X Archive Daemon environment.
This tool retrieves posts from X via a search query and writes them into the local SQLite database. The primary side effect is creating/inserting new records into the archive, making it a Write operation. It is not Destructive (no deletion), not Financial, and not Execute (no arbitrary code execution).
From the tool's definition Fetches posts matching an X search query and stores them in the local archive
Attacks that exploit this kind of access
Fetches posts matching an X search query and stores them in the local archive. It is categorised as a Write tool in the X Archive Daemon MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the X Archive Daemon MCP server in PolicyLayer and add a rule for ingest.search.backfill: 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.
ingest.search.backfill is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the ingest.search.backfill 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 ingest.search.backfill. 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.
ingest.search.backfill 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 →