Looks up each submitted domain in the TunnelMind tracker database, aggregates risk metrics (avg score, max score, fingerprinters, high-risk domains, entity ownership), and issues a signed surveillance receipt. The receipt is stored in the public registry and can be verified at /verify/{receipt_id...
Part of the TunnelMind Data API server.
Free to start. No card required.
AI agents use generate_receipt to create or modify resources in TunnelMind Data API. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call generate_receipt repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach TunnelMind Data API.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"generate_receipt": {
"limits": [
{
"counter": "generate_receipt_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full TunnelMind Data API policy for all 54 tools.
These attack patterns abuse exactly the kind of access generate_receipt gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Looks up each submitted domain in the TunnelMind tracker database, aggregates risk metrics (avg score, max score, fingerprinters, high-risk domains, entity ownership), and issues a signed surveillance receipt. The receipt is stored in the public registry and can be verified at /verify/{receipt_id}. Use this tool when: - You want a verifiable record of which trackers were observed in a context (page, app, session). - You need a signed evidence artifact for a privacy audit or compliance report. - You want to know the overall surveillance exposure level for a set of domains. - You are generating a receipt to share with a user as evidence of tracker presence. Do NOT use this tool when: - You want full tracker details per domain — use get_domain instead. - You want to look up an existing receipt — use get_receipt instead. - You need live probes (HTTP headers, stack detection) — use /v1/intel/* instead. Inputs: - domains (body, required): Array of 1–50 fully qualified domain names. Duplicates are deduplicated. URLs are stripped to host component. - domain (body, alternative): Single domain string (shorthand for domains: [domain]). Returns: - receipt_id: Unique receipt ID (e.g. rcpt_01JXYZ...). - receipt: Full receipt document including domains submitted, tracker findings, high-risk domains, fingerprinters, unique entities, and exposure metrics. - content_hash: SHA-256 of the canonical receipt JSON. - signature: Base64 Ed25519 signature (empty string if signing key not configured). - signed: Boolean — true if the receipt is cryptographically signed. - verify_url: Path to retrieve this receipt from the public registry. Exposure levels: minimal / moderate / high / critical Based on average tracker score and proportion of high-risk domains (score ≥ 70). Cost: - Counts as one request against the daily limit regardless of domain count. Latency: - Typical: <100ms (pure D1 lookup, no outbound probing). p99: <300ms.. It is categorised as a Write tool in the TunnelMind Data API MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TunnelMind Data API MCP server in PolicyLayer and add a rule for generate_receipt: 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.
generate_receipt is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the generate_receipt 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 generate_receipt. 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.
generate_receipt 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.