Low Risk

garl_receipt

Fetch a public, shareable GARL Receipt for any trace hash. Works without an API key. Accepts either a full 64-char SHA-256 hash or a short 8-63 char prefix (as seen in garl.ai/r/{short} URLs). Returns the shareable receipt URL plus agent name, tier, task description, duration, status and ECDSA si...

Part of the Garl Protocol server.

garl_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 GARL PROTOCOL →

Free to start. No card required.

AI agents call garl_receipt to retrieve information from Garl Protocol 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 garl_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": {
    "garl_receipt": {}
  }
}

See the full Garl Protocol policy for all 28 tools.

Get this rule live on your own Garl Protocol server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY GARL PROTOCOL →

View all 28 tools →

These attack patterns abuse exactly the kind of access garl_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 garl_receipt only ever does what you allow.

SECURE GARL PROTOCOL →

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

What does the garl_receipt tool do? +

Fetch a public, shareable GARL Receipt for any trace hash. Works without an API key. Accepts either a full 64-char SHA-256 hash or a short 8-63 char prefix (as seen in garl.ai/r/{short} URLs). Returns the shareable receipt URL plus agent name, tier, task description, duration, status and ECDSA signature. Use this after garl_verify to grab a paste-ready proof link, or to inspect any public trace from a URL.. It is categorised as a Read tool in the Garl Protocol MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on garl_receipt? +

Register the Garl Protocol MCP server in PolicyLayer and add a rule for garl_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 Garl Protocol. Nothing to install.

What risk level is garl_receipt? +

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

Can I rate-limit garl_receipt? +

Yes. Add a rate_limit block to the garl_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 garl_receipt completely? +

Set action: deny in the PolicyLayer policy for garl_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 garl_receipt? +

garl_receipt is provided by the Garl Protocol MCP server (@garl-protocol/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Garl Protocol tool call.

Deterministic rules across all 28 Garl Protocol 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.