lens_reply · Lens MCP: Risk & Policy

WHAT IT DOES

What lens_reply does on Lens

AI agents use lens_reply to create or update resources in Lens — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lens environment.

WHY IT NEEDS A POLICY

Why lens_reply needs a policy

The tool creates a new reply/message in an annotation thread, which is a reversible write operation (the reply could be deleted). It modifies data by adding content to an existing thread but does not delete or irreversibly alter anything, nor does it execute code or involve finances.

From the tool's definition Reply to an annotation thread

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

lens_reply Rate-limited

lens_reply stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "lens_reply": {
      "limits": [
        {
          "counter": "lens_reply_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Lens, so you can run agents against it safely.

FAQ

Questions about lens_reply

What does the lens_reply tool do? +

Reply to an annotation thread. It is categorised as a Write tool in the 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 lens_reply? +

Register the Lens MCP server in PolicyLayer and add a rule for lens_reply: 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 Lens. Nothing to install.

What risk level is lens_reply? +

lens_reply is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit lens_reply? +

Yes. Add a rate_limit block to the lens_reply 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 lens_reply completely? +

Set action: deny in the PolicyLayer policy for lens_reply. 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 lens_reply? +

lens_reply is provided by the Lens MCP server (renderdraw/lens). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.