search_lenses
Search public lens catalog rows. Use when the user asks for real lens part numbers, links, focal lengths, diameters, coatings, or purchasable candidates for a design. Return matches as evidence; never claim a part exists unless it appears in the result.
This record as markdown: /tools/com-gaussian-beam-diffbeam/search-lenses.md
What search_lenses does on DiffBeam Gaussian Beam Optics
AI agents call search_lenses to retrieve information from DiffBeam Gaussian Beam Optics without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Maximum catalog matches to return. |
query | string | Yes | Part number or short component phrase. Use vendor-neutral physics terms unless the user names a vendor or part family. |
diameter_mm | object | — | Optional desired optic diameter in millimetres, used for ranking. |
wavelength_nm | object | — | Optional operating wavelength in nanometres. |
focal_length_mm | object | — | Optional desired focal length in millimetres, used for ranking. |
Parameters from the server's own tool schema.
Why search_lenses is rated Low
Even though search_lenses only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs search_lenses safely
PolicyLayer is an MCP gateway: it sits between your AI agents and DiffBeam Gaussian Beam Optics, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_lenses, this is the rule to start with:
search_lenses is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect DiffBeam Gaussian Beam Optics, apply this rule, and every search_lenses call is checked against it from then on.
Questions about search_lenses
Search public lens catalog rows. Use when the user asks for real lens part numbers, links, focal lengths, diameters, coatings, or purchasable candidates for a design. Return matches as evidence; never claim a part exists unless it appears in the result. It is categorised as a Read tool in the DiffBeam Gaussian Beam Optics MCP Server, which means it retrieves data without modifying state.
search_lenses accepts 5 parameters: limit, query, diameter_mm, wavelength_nm, focal_length_mm. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the DiffBeam Gaussian Beam Optics MCP server in PolicyLayer and add a rule for search_lenses: 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 DiffBeam Gaussian Beam Optics. Nothing to install.
search_lenses 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 search_lenses 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 search_lenses. 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.
search_lenses is provided by the DiffBeam Gaussian Beam Optics MCP server (https://catalog-api.gaussian-beam.com/mcp/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on DiffBeam Gaussian Beam Optics, and thousands of servers like it.
This server
Across the catalogue