Low Risk

get_lens_data

Return current Reporecall Lens JSON from the existing index. Read-only; call refresh_context first when fresh indexing/wiki generation is required.

How to control get_lens_data ↓

AI agents call get_lens_data to retrieve information from Reporecall without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves structured data (JSON) from an existing index without modifying, deleting, or executing any operations. The explicit 'Read-only' designation confirms it has no side effects and fits the Read category (retrieves or queries data; no side effects).

From the tool's definition Tool description explicitly states 'Return current Reporecall Lens JSON from the existing index' and 'Read-only'

Documented attack patterns abuse exactly the kind of access get_lens_data gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Reporecall, and nothing reaches the server without passing your rules. This is the rule we recommend for get_lens_data:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_lens_data": {}
  }
}

get_lens_data is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Reporecall — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_lens_data tool do? +

Return current Reporecall Lens JSON from the existing index. Read-only; call refresh_context first when fresh indexing/wiki generation is required. It is categorised as a Read tool in the Reporecall MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_lens_data? +

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

What risk level is get_lens_data? +

get_lens_data is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_lens_data? +

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

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

get_lens_data is provided by the Reporecall MCP server (proofofwork-agency/reporecall). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Reporecall tool call.

Deterministic rules across all 30 Reporecall tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

30 Reporecall tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.