# knowledge_search

Search the knowledge base for information from ingested documents. Use this when the user asks questions that might be answered by their personal documents in the knowledge folder. This searches ONLY the knowledge namespace, not conversational memories.

Agent View of the PolicyLayer registry record for `knowledge_search`. HTML page: https://policylayer.com/tools/0xcjt-templonixlite/knowledge-search

## Facts

- Tool: `knowledge_search`
- Server: Templonix Lite MCP Server (`0xcjt/templonixlite`) — https://policylayer.com/tools/0xcjt-templonixlite.md
- Homepage: https://github.com/0xCJT/TemplonixLite
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "knowledge_search",
    "arguments": {}
  }
}
```

## Why knowledge_search is rated Low

This tool performs a query operation on stored documents to retrieve information. There is no modification, deletion, execution of code, or financial impact. The operation is purely informational and non-destructive, fitting the Read category with low severity as misuse would only result in unintended information disclosure rather than data loss or system compromise.

From the tool's own definition: "Tool description states it 'Search[es] the knowledge base for information from ingested documents' and 'searches ONLY the knowledge namespace'. The verb 'search' and the read-only nature of querying ingested documents indicates retrieval without side effects."

## Use case

AI agents call knowledge_search 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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Templonix Lite MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "knowledge_search": {}
  }
}
```

## Other tools on Templonix Lite MCP Server (17)

- `archive_purge` — Destructive — https://policylayer.com/tools/0xcjt-templonixlite/archive-purge.md
- `calendar_delete_event` — Destructive — https://policylayer.com/tools/0xcjt-templonixlite/calendar-delete-event.md
- `knowledge_clear` — Destructive — https://policylayer.com/tools/0xcjt-templonixlite/knowledge-clear.md
- `diagram_create` — Execute — https://policylayer.com/tools/0xcjt-templonixlite/diagram-create.md
- `archive_search` — Read — https://policylayer.com/tools/0xcjt-templonixlite/archive-search.md
- `archive_search_all` — Read — https://policylayer.com/tools/0xcjt-templonixlite/archive-search-all.md
- `archive_stats` — Read — https://policylayer.com/tools/0xcjt-templonixlite/archive-stats.md
- `calendar_list_events` — Read — https://policylayer.com/tools/0xcjt-templonixlite/calendar-list-events.md
- `jina_search` — Read — https://policylayer.com/tools/0xcjt-templonixlite/jina-search.md
- `knowledge_stats` — Read — https://policylayer.com/tools/0xcjt-templonixlite/knowledge-stats.md
- `workflow_get` — Read — https://policylayer.com/tools/0xcjt-templonixlite/workflow-get.md
- `workflow_list` — Read — https://policylayer.com/tools/0xcjt-templonixlite/workflow-list.md
- `archive_insert` — Write — https://policylayer.com/tools/0xcjt-templonixlite/archive-insert.md
- `calendar_create_event` — Write — https://policylayer.com/tools/0xcjt-templonixlite/calendar-create-event.md
- `email_save_draft` — Write — https://policylayer.com/tools/0xcjt-templonixlite/email-save-draft.md
- `email_send` — Write — https://policylayer.com/tools/0xcjt-templonixlite/email-send.md
- `knowledge_load` — Write — https://policylayer.com/tools/0xcjt-templonixlite/knowledge-load.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=0xcjt-templonixlite · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0xcjt-templonixlite