AI agents call google_lens_detect to retrieve information from Noapi Google Search without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the tool name and server description mentioning OCR capabilities, this tool likely performs image analysis/detection via Google Lens, which is a read/query operation with no side effects. Confidence is lowered due to empty description.
From the tool's definition Tool name 'google_lens_detect' and server context involving OCR and open-source models; description is empty
Documented attack patterns abuse exactly the kind of access google_lens_detect gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Noapi Google Search, and nothing reaches the server without passing your rules. This is the rule we recommend for google_lens_detect:
{
"version": "1",
"default": "deny",
"tools": {
"google_lens_detect": {}
}
}google_lens_detect is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
google_lens_detect. It is categorised as a Read tool in the Noapi Google Search MCP Server, which means it retrieves data without modifying state.
Register the Noapi Google Search MCP server in PolicyLayer and add a rule for google_lens_detect: 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 Noapi Google Search. Nothing to install.
google_lens_detect 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 google_lens_detect 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 google_lens_detect. 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.
google_lens_detect is provided by the Noapi Google Search MCP server (vincentkaufmann/noapi-google-search-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 38 Noapi Google Search tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
38 Noapi Google Search tools catalogued and risk-classified — across an index of 42,500+ MCP servers.