Low Risk

get_receipt

Returns metadata for a TunnelMind surveillance receipt — a signed document proving that a specific user's surveillance exposure was observed, measured, and recorded at a specific time. Does NOT return the receipt's signature (anti-phishing protection). To verify a receipt's content integrity, use...

Part of the TunnelMind Data API server.

get_receipt 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 get_receipt 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 get_receipt 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": {
    "get_receipt": {}
  }
}

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 get_receipt 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 get_receipt 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 get_receipt tool do? +

Returns metadata for a TunnelMind surveillance receipt — a signed document proving that a specific user's surveillance exposure was observed, measured, and recorded at a specific time. Does NOT return the receipt's signature (anti-phishing protection). To verify a receipt's content integrity, use verify_receipt with the hash and signature from the receipt document itself. Use this tool when: - You have a receipt ID and want to confirm it was genuinely issued by TunnelMind. - You need the issuance timestamp and signing key ID for a receipt. - You want to check whether a receipt exists before attempting content verification. Do NOT use this tool when: - You have the full receipt document and want to verify it hasn't been tampered with — use verify_receipt instead. Inputs: - receipt_id (path, required): The receipt ID from the receipt document. Alphanumeric with hyphens, max 128 characters. Returns: - status: FOUND if the receipt is in the registry. - generated_at: ISO 8601 timestamp of receipt issuance. - signing_key_id: identifier of the Ed25519 key used to sign. - schema_version: receipt schema version. - message: human-readable summary with instructions for content verification. - 404 if the receipt ID is not in the registry. Cost: - Free. No API key required. Latency: - Typical: <100ms, p99: <300ms.. 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 get_receipt? +

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

What risk level is get_receipt? +

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

Can I rate-limit get_receipt? +

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

How do I block get_receipt completely? +

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

What MCP server provides get_receipt? +

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

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.