// MCP TOOL REFERENCE

CONTEXT LENS TOOLS

6 tools from the Context Lens MCP Server, categorised by risk level.

// ALL 6 CONTEXT LENS TOOLS

READ 3 tools

Read 📋 list_documents Browse all indexed documents Read 🔍 search_documents Semantic search across all indexed content Read ℹ️ get_document_info Get metadata about a specific document

WRITE 1 tools

Write 📥 add_document Add files, folders, or GitHub URLs to knowledge base

DESTRUCTIVE 2 tools

Destructive 🗑️ remove_document Remove a specific document from the index Destructive 🧹 clear_knowledge_base Remove all documents from the knowledge base

// RUNNING THIS SERVER

The managed route: connect Context Lens through the PolicyLayer gateway — every tool call above is checked against your policy before it runs, with a full audit log.

DIRECT INSTALL (UNMANAGED) npx -y context-lens

// FAQ

How many tools does the Context Lens MCP server have? +

The Context Lens MCP server exposes 6 tools across 3 categories: Read, Write, Destructive.

How do I enforce policies on Context Lens tools? +

Route the Context Lens server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard — they are enforced on every call before it reaches the server.

What risk categories do Context Lens tools fall into? +

Context Lens tools are categorised as Read (3), Write (1), Destructive (2). Each category has a recommended default policy.

Let agents act without letting them run wild.

Route your MCP servers through PolicyLayer and every tool call is checked against your policy before it runs — allow, deny, or require approval. Per-identity grants. Full audit log. Live in minutes.

SECURE YOUR MCP →

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.