A2 — the cross-lens join. TunnelMind owns both halves of the open-web graph: Scry sees who is on every IP (attacker intelligence, actor class, Augur threat-intel overlap); Sigil sees the supply graph (publishers, SSPs, DSPs, ads.txt + sellers.json + SupplyChain Object). This endpoint fuses them i...
Part of the TunnelMind Data API server.
Free to start. No card required.
AI agents call cross_lens_verify to retrieve information from TunnelMind Data API without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though cross_lens_verify only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"cross_lens_verify": {}
}
}See the full TunnelMind Data API policy for all 54 tools.
These attack patterns abuse exactly the kind of access cross_lens_verify gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
A2 — the cross-lens join. TunnelMind owns both halves of the open-web graph: Scry sees who is on every IP (attacker intelligence, actor class, Augur threat-intel overlap); Sigil sees the supply graph (publishers, SSPs, DSPs, ads.txt + sellers.json + SupplyChain Object). This endpoint fuses them into one verdict on a single node key. The response contains three blocks: - scry — the single-lens Scry view (transparency). - sigil — the single-lens Sigil view (transparency). - cross_lens — the fused verdict (the moat). Fusion math: weighted-mean over evaluated components plus a co_observation_bonus when both lenses independently flag the node. Weights and thresholds are per-request overridable. Lens unavailability is reported in-band: each lens fails independently and the cross_lens block reflects degraded confidence when only one lens has data. Returns 503 only when BOTH lenses are unavailable. v1 lens coverage matrix: - IP node — Scry: full; Sigil: not_indexed (v2 will reverse-DNS). - Domain node — Scry: deferred; Sigil: full (publisher/ssp/dsp + entity). - entity_slug node — Scry: n/a; Sigil: full (entity + sell/buy presence). - ASN node — Scry: deferred (v2); Sigil: not_indexed.. It is categorised as a Read tool in the TunnelMind Data API MCP Server, which means it retrieves data without modifying state.
Register the TunnelMind Data API MCP server in PolicyLayer and add a rule for cross_lens_verify: 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 TunnelMind Data API. Nothing to install.
cross_lens_verify 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 cross_lens_verify 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 cross_lens_verify. 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.
cross_lens_verify is provided by the TunnelMind Data API MCP server (https://mcp-data.tunnelmind.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 54 TunnelMind Data API tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.