Archive completed tasks via auto-action engine. Moves all [x] tasks from today and backlog to archive.md with timestamps. Part of the auto-optimization system.
AI agents use autoArchive to create or update resources in Knowledge MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Knowledge MCP Server environment.
This tool writes/modifies markdown files by reorganizing task data into an archive file. While it affects multiple files, the operation is reversible (tasks are moved, not deleted), and the blast radius is limited to the user's personal knowledge base structure with no external side effects, external code execution, or data destruction.
From the tool's definition Tool description states it 'Moves all [x] tasks from today and backlog to archive.md with timestamps,' indicating a write operation that modifies files by moving (copying) data to archive.md.
Attacks that exploit this kind of access
Archive completed tasks via auto-action engine. Moves all [x] tasks from today and backlog to archive.md with timestamps. Part of the auto-optimization system. It is categorised as a Write tool in the Knowledge MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Knowledge MCP Server MCP server in PolicyLayer and add a rule for autoArchive: 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 Knowledge MCP Server. Nothing to install.
autoArchive 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 autoArchive 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 autoArchive. 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.
autoArchive is provided by the Knowledge MCP Server MCP server (vuluu2k/knowledge_mcp). 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 →