Verify a full OpenRTB SupplyChain (schain) object — every node, end to end. Per node Sigil checks the seller against the exchange sellers.json and the origin ads.txt, then returns a per-node and aggregate verdict plus a signed token. Use this tool when: - A bid request carries an OpenRTB schain a...
Risk signalsBulk/mass operation — affects multiple targets
Part of the Sigil server.
Free to start. No card required.
AI agents call sigil_verify_supply_chain 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 sigil_verify_supply_chain 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": {
"sigil_verify_supply_chain": {}
}
}See the full Sigil policy for all 12 tools.
These attack patterns abuse exactly the kind of access sigil_verify_supply_chain 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.
Verify a full OpenRTB SupplyChain (schain) object — every node, end to end. Per node Sigil checks the seller against the exchange sellers.json and the origin ads.txt, then returns a per-node and aggregate verdict plus a signed token. Use this tool when: - A bid request carries an OpenRTB schain and you want it verified verbatim. Inputs: - schain (required): an OpenRTB SupplyChain object ({ ver, complete, nodes:[{asi,sid,hp}] }). - site_domain or app_bundle (optional): the inventory origin, checked against node[0] via ads.txt / OWNERDOMAIN. Returns: per-node nodes results, an aggregate verdict, recommendations, and a signed sigil_token.. 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 sigil_verify_supply_chain: 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.
sigil_verify_supply_chain 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 sigil_verify_supply_chain 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 sigil_verify_supply_chain. 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.
sigil_verify_supply_chain 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.