Context Lens

6 tools. 3 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated:

3 can modify or destroy data
3 read-only
6 tools total

3 Context Lens tools can modify or destroy data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE CONTEXT LENS →

Free to start. No card required.

Read (3) Write / Execute (1) Destructive / Financial (2)

Destructive tools (๐Ÿ—‘๏ธ remove_document, ๐Ÿงน clear_knowledge_base) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.

Write operations (๐Ÿ“ฅ add_document) modify state. Without rate limits, an agent can make hundreds of changes in seconds โ€” faster than any human can review or revert.

Deny destructive operations
{
  "๐Ÿ—‘๏ธ remove_document": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "๐Ÿ“ฅ add_document": {
    "limits": [
      {
        "counter": "๐Ÿ“ฅ add_document_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "๐Ÿ“‹ list_documents": {
    "limits": [
      {
        "counter": "๐Ÿ“‹ list_documents_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Get this policy live on your own Context Lens server in minutes. Tune the limits to your setup; PolicyLayer enforces it on every call.

ENFORCE ON MY CONTEXT LENS →
Can an AI agent delete data through the Context Lens MCP server? +

Yes. The Context Lens server exposes 2 destructive tools including ๐Ÿ—‘๏ธ remove_document, ๐Ÿงน clear_knowledge_base. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Context Lens? +

The Context Lens server has 1 write tools including ๐Ÿ“ฅ add_document. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Context Lens.

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

6 tools across 3 categories: Destructive, Read, Write. 3 are read-only. 3 can modify, create, or delete data.

How do I enforce a policy on Context Lens? +

Register the Context Lens MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Other MCP servers with similar tools.

Starter policies for each. Same risk classification, live on your fleet in minutes.

Enforce policy on every Context Lens tool call.

Deterministic rules across all 6 Context Lens tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

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

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.