Analyzes already archived posts locally, adds educational/topic signals, and stores insights. Works for both old and newly ingested posts.
AI agents use analysis.posts.run 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.
The tool reads existing archived posts and then writes new derived data (topic labels, educational signals, insights) back into the local SQLite database. This is a reversible write operation — no data is deleted and no external systems are affected. Severity is medium because an AI agent could pollute the archive with incorrect or misleading topic signals at scale, degrading the quality of future semantic searches.
From the tool's definition 'analyzes already archived posts locally, adds educational/topic signals, and stores insights' — modifies stored records by appending new analytical metadata
Attacks that exploit this kind of access
Analyzes already archived posts locally, adds educational/topic signals, and stores insights. Works for both old and newly ingested posts. 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 analysis.posts.run: 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.
analysis.posts.run 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 analysis.posts.run 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 analysis.posts.run. 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.
analysis.posts.run 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.
analysis.posts.run is one line of X Archive Daemon's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →