Read the task archive for a specific month. Defaults to current month. Use when the user asks
AI agents call getArchive to retrieve information from Knowledge MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves archived task data from a knowledge base without creating, modifying, deleting, or executing any operations. It is a simple data retrieval function that queries historical task information. The low severity reflects the minimal blast radius—an AI agent misusing this would at worst read unintended archived tasks, causing no side effects or data loss.
From the tool's definition Tool name 'getArchive' and description 'Read the task archive for a specific month' explicitly indicates a read operation with no modification capability.
Attacks that exploit this kind of access
Read the task archive for a specific month. Defaults to current month. Use when the user asks. It is categorised as a Read tool in the Knowledge MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Knowledge MCP Server MCP server in PolicyLayer and add a rule for getArchive: 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.
getArchive 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 getArchive 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 getArchive. 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.
getArchive 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 →