AI agents call lens_get_session to retrieve information from Lens without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about an annotation session and its associated project context. There are no side effects, no data modification, no code execution, and no destructive operations. It is a straightforward query/fetch operation that returns contextual information for routing purposes.
From the tool's definition Tool description states 'Get a specific annotation session by ID or URL' — a retrieval operation with no modification capability. The word 'Get' and the retrieval-only nature (fetching project context data) confirm this is a read operation.
Attacks that exploit this kind of access
Get a specific annotation session by ID or URL. Includes project context (slug, name, repo) for routing to the correct codebase. It is categorised as a Read tool in the Lens MCP Server, which means it retrieves data without modifying state.
Register the Lens MCP server in PolicyLayer and add a rule for lens_get_session: 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.
lens_get_session is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the lens_get_session 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.
Set action: deny in the PolicyLayer policy for lens_get_session. 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.
lens_get_session 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →