Low Risk

check_receipt_revoked

Single-item revocation lookup per Receipt Format v1.0 §8.2. Verifiers that do not want to maintain a local mirror of /.well-known/receipt-revocations.json call this endpoint instead. The response includes feed_version for cache coherence. Use this tool when: - You are verifying a receipt and need...

Part of the TunnelMind Data API server.

check_receipt_revoked is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE TUNNELMIND DATA API →

Free to start. No card required.

AI agents call check_receipt_revoked 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 check_receipt_revoked 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_receipt_revoked": {}
  }
}

See the full TunnelMind Data API policy for all 54 tools.

Get this rule live on your own TunnelMind Data API server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY TUNNELMIND DATA API →

View all 54 tools →

These attack patterns abuse exactly the kind of access check_receipt_revoked gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so check_receipt_revoked only ever does what you allow.

SECURE TUNNELMIND DATA API →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the check_receipt_revoked tool do? +

Single-item revocation lookup per Receipt Format v1.0 §8.2. Verifiers that do not want to maintain a local mirror of /.well-known/receipt-revocations.json call this endpoint instead. The response includes feed_version for cache coherence. Use this tool when: - You are verifying a receipt and need to confirm its signature.key_id is still trusted. - You are verifying a receipt and need to confirm the specific receipt_id was not retracted by its issuer. - You hold receipts long-term and want to recheck trust before acting on them. Do NOT use this tool when: - You want the full revocation set — fetch /.well-known/receipt-revocations.json directly. - You want to *publish* a revocation — that is operator-controlled and not exposed via this API. Inputs: - key_id (query, optional): Receipt-format key_id (e.g., tm-receipt-2026-05). Provide one of key_id or id. - id (query, optional): UUIDv7 of a specific receipt. Provide one of key_id or id. Returns: - revoked: boolean. - When revoked: revoked_at (ISO 8601), reason (human-readable), replacement_key_id (for keys). - Always: checked_at (ISO 8601), feed_version (integer). Cost: - Free; rate-limited like the rest of the data API. Edge-cached 60s. Latency: - Typical <100ms (warm cache); p99 <500ms (cold fetch from well-known).. It is categorised as a Read tool in the TunnelMind Data API MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_receipt_revoked? +

Register the TunnelMind Data API MCP server in PolicyLayer and add a rule for check_receipt_revoked: 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.

What risk level is check_receipt_revoked? +

check_receipt_revoked is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_receipt_revoked? +

Yes. Add a rate_limit block to the check_receipt_revoked 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.

How do I block check_receipt_revoked completely? +

Set action: deny in the PolicyLayer policy for check_receipt_revoked. 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.

What MCP server provides check_receipt_revoked? +

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

Enforce policy on every TunnelMind Data API tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.