📜 HISTORY: List all changes made to the knowledge base in human-friendly format. Shows both file uploads and knowledge base generations separately. Example: repositoryId=
AI agents call lspace_list_knowledge_base_history to retrieve information from Lspace 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 and displays historical information about knowledge base modifications. It performs a query operation to enumerate past changes without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an attacker could gain visibility into knowledge base history but cannot alter or destroy data through this tool alone.
From the tool's definition Tool description indicates it "List[s] all changes made to the knowledge base" and "Shows both file uploads and knowledge base generations separately." The verb 'List' and the read-only nature of querying history demonstrates this is a retrieval operation…
Documented attack patterns abuse exactly the kind of access lspace_list_knowledge_base_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Lspace MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for lspace_list_knowledge_base_history:
{
"version": "1",
"default": "deny",
"tools": {
"lspace_list_knowledge_base_history": {}
}
}lspace_list_knowledge_base_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
📜 HISTORY: List all changes made to the knowledge base in human-friendly format. Shows both file uploads and knowledge base generations separately. Example: repositoryId=. It is categorised as a Read tool in the Lspace MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Lspace MCP Server MCP server in PolicyLayer and add a rule for lspace_list_knowledge_base_history: 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 Lspace MCP Server. Nothing to install.
lspace_list_knowledge_base_history 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 lspace_list_knowledge_base_history 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 lspace_list_knowledge_base_history. 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.
lspace_list_knowledge_base_history is provided by the Lspace MCP Server MCP server (lspace-io/lspace-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Lspace MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 Lspace MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.