Medium Risk

๐Ÿ“ฅ add_document

Add files, folders, or GitHub URLs to knowledge base

Risk signalsIndexes external content into the system

Part of the Context Lens server.

๐Ÿ“ฅ add_document can modify Context Lens 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.

AI agents use ๐Ÿ“ฅ add_document to create or modify resources in Context Lens. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call ๐Ÿ“ฅ add_document repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Context Lens.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "๐Ÿ“ฅ add_document": {
      "limits": [
        {
          "counter": "๐Ÿ“ฅ add_document_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Context Lens policy for all 6 tools.

Get this rule live on your own Context Lens server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY CONTEXT LENS →

These attack patterns abuse exactly the kind of access ๐Ÿ“ฅ add_document gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so ๐Ÿ“ฅ add_document only ever does what you allow.

SECURE CONTEXT LENS →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the ๐Ÿ“ฅ add_document tool do? +

Add files, folders, or GitHub URLs to knowledge base. It is categorised as a Write tool in the Context Lens MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on ๐Ÿ“ฅ add_document? +

Register the Context Lens MCP server in PolicyLayer and add a rule for ๐Ÿ“ฅ add_document: 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 Context Lens. Nothing to install.

What risk level is ๐Ÿ“ฅ add_document? +

๐Ÿ“ฅ add_document is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit ๐Ÿ“ฅ add_document? +

Yes. Add a rate_limit block to the ๐Ÿ“ฅ add_document 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.

How do I block ๐Ÿ“ฅ add_document completely? +

Set action: deny in the PolicyLayer policy for ๐Ÿ“ฅ add_document. 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.

What MCP server provides ๐Ÿ“ฅ add_document? +

๐Ÿ“ฅ add_document is provided by the Context Lens MCP server (context-lens). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

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.