# 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.

Agent View of the PolicyLayer registry record for `search_lenses`. HTML page: https://policylayer.com/tools/com-gaussian-beam-diffbeam/search-lenses

## Facts

- Tool: `search_lenses`
- Server: DiffBeam Gaussian Beam Optics (`https://catalog-api.gaussian-beam.com/mcp/`) — https://policylayer.com/tools/com-gaussian-beam-diffbeam.md
- Homepage: https://github.com/RiaRosenauer/diffbeam-mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 5 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `limit` | integer | no | 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 | no | Optional desired optic diameter in millimetres, used for ranking. |
| `wavelength_nm` | object | no | Optional operating wavelength in nanometres. |
| `focal_length_mm` | object | no | Optional desired focal length in millimetres, used for ranking. |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "search_lenses",
    "arguments": {
      "query": "<query>"
    }
  }
}
```

## 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.

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches DiffBeam Gaussian Beam Optics:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_lenses": {}
  }
}
```

## Other tools on DiffBeam Gaussian Beam Optics (3)

- `get_diffbeam_state` — Read — https://policylayer.com/tools/com-gaussian-beam-diffbeam/get-diffbeam-state.md
- `search_fiber_collimators` — Read — https://policylayer.com/tools/com-gaussian-beam-diffbeam/search-fiber-collimators.md
- `search_fibers` — Read — https://policylayer.com/tools/com-gaussian-beam-diffbeam/search-fibers.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-gaussian-beam-diffbeam · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-gaussian-beam-diffbeam