archive_search_all
Search across BOTH knowledge documents AND conversational memories. Use this when the user's question might be answered by either source, when you need a comprehensive view, or when you're unsure which namespace contains the relevant information. Results are clearly labelled by source type.
This record as markdown: /tools/0xcjt-templonixlite/archive-search-all.md
What archive_search_all does on Templonix Lite MCP Server
AI agents call archive_search_all to retrieve information from Templonix Lite MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why archive_search_all is rated Low
This tool only retrieves and queries data from two namespaces (knowledge documents and conversational memories). It has no side effects, does not modify or delete data, and is purely a read/search operation.
From the tool's definition Search across BOTH knowledge documents AND conversational memories... Results are clearly labelled by source type.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs archive_search_all safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Templonix Lite MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For archive_search_all, this is the rule to start with:
archive_search_all is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Templonix Lite MCP Server, apply this rule, and every archive_search_all call is checked against it from then on.
Questions about archive_search_all
Search across BOTH knowledge documents AND conversational memories. Use this when the user's question might be answered by either source, when you need a comprehensive view, or when you're unsure which namespace contains the relevant information. Results are clearly labelled by source type. It is categorised as a Read tool in the Templonix Lite MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Templonix Lite MCP Server MCP server in PolicyLayer and add a rule for archive_search_all: 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 Templonix Lite MCP Server. Nothing to install.
archive_search_all 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 archive_search_all 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 archive_search_all. 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.
archive_search_all is provided by the Templonix Lite MCP Server MCP server (0xcjt/templonixlite). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Templonix Lite MCP Server, and thousands of servers like it.
This server
Across the catalogue