A2 — the cross-lens join. Fuse TunnelMind's two lenses (Scry attacker intelligence + Sigil supply graph) into ONE verdict on a single node key. This is the moat: no siloed competitor owns both halves of the graph, so the fused cross_lens block carries information neither lens can supply alone. Us...
Part of the Sigil server.
Free to start. No card required.
AI agents call cross_lens_verify to retrieve information from Sigil 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 Sigil policy for all 12 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. Fuse TunnelMind's two lenses (Scry attacker intelligence + Sigil supply graph) into ONE verdict on a single node key. This is the moat: no siloed competitor owns both halves of the graph, so the fused cross_lens block carries information neither lens can supply alone. Use this tool when: - An agent must decide whether to transact with an IP, domain, ASN, or entity_slug, and a one-lens answer is not enough. - You want a single composite trust verdict instead of running Scry + Sigil calls separately and reconciling them by hand. Inputs: - node (required): an IPv4 address, a domain, an ASN (e.g. AS64500), or an entity_slug. Type is auto-detected. - weights (optional): per-component weight overrides. - thresholds (optional): { pass, fail } verdict cutoffs (defaults 0.7 / 0.3). - ait (optional): an ATAP AIT id. When present, the verdict is chained onto the AIT as a witness-tier cross_lens:verified event signed by Sigil (witness OAI-2026-0000201) — replayable evidence, not just JSON. Returns: per-lens scry + sigil blocks (transparency), a fused cross_lens block with verdict / trust_score / confidence / signals / recommendations, a 5-minute signed sigil_token, and a witnessed_event block when an AIT was supplied. Failure semantics: each lens fails independently. Single-lens answers still return 200 with a confidence of 0.55. Returns 503 only when BOTH lenses are unavailable.. It is categorised as a Read tool in the Sigil MCP Server, which means it retrieves data without modifying state.
Register the Sigil 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 Sigil. 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 Sigil MCP server (https://mcp.sigil.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 12 Sigil 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.