otlp_span_receipt

SERVERAinumbers Mcp Apps SOURCEpostoaklabs/ainumbers-mcp-apps

High RISK CLASS

Category Execute

Parameters 40 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/postoaklabs-ainumbers-mcp-apps/otlp-span-receipt.md

WHAT IT DOES

What otlp_span_receipt does on Ainumbers Mcp Apps

AI agents invoke otlp_span_receipt to trigger actions in Ainumbers Mcp Apps. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`trace`	object	—	An OTLP/JSON trace document to generate a receipt bundle over. Omit if passing bundle or run_chain_result.
`bundle`	object	—	{trace, span_receipts[], trace_receipt, issuer_did} to VERIFY instead of generate.
`service`	string	—	resource service.name to stamp when bridging run_chain_result into a trace. Defaults to "ainumbers-chaingraph-worker".
`run_chain_result`	object	—	The structuredContent object returned by run_chain (must include chain and steps[]) -- bridges the chain run into an OTLP trace, then generates a receipt bundle

Parameters from the server's own tool schema.

RISK

Why otlp_span_receipt is rated High

Tool executes cryptographic operations and builds signed receipt bundles from trace data.

From the tool's definition generates receipt bundle, computes digests, eddsa signatures, Merkle root

Risk signalsBulk/mass operation — affects multiple targets · Admin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs otlp_span_receipt safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ainumbers Mcp Apps, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For otlp_span_receipt, this is the rule to start with:

otlp_span_receipt Rate-limited

otlp_span_receipt stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "otlp_span_receipt": {
      "limits": [
        {
          "counter": "otlp_span_receipt_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ainumbers Mcp Apps, apply this rule, and every otlp_span_receipt call is checked against it from then on.

FAQ

Questions about otlp_span_receipt

What does the otlp_span_receipt tool do? +

OTLP span/trace to receipt bundle; does NOT build a ChainGraph (use build_chaingraph for that). Three modes, chosen by which input is supplied. (1) Pass trace alone to GENERATE a receipt bundle: a per-span receipt (span digest, parent-span receipt digest, semconv_snapshot, eddsa-jcs-2022 signature over an ephemeral did:key) for every span, plus a Merkle-rooted (RFC 6962) trace receipt. (2) Pass bundle ({trace, span_receipts, trace_receipt, issuer_did}) to VERIFY it: recomputes every digest, walks the parent-receipt chain, rebuilds the Merkle root, and reports which spans are attested, unattested, or tampered. (3) Pass run_chain_result (the structuredContent from run_chain) instead of trace to bridge a ChainGraph chain run into an OTLP trace first -- one execute_tool span per successfully-executed step, each carrying its own execution_hash as a span attribute (ocg.execution_hash) -- then generates the same receipt bundle over it. Byte-identical receipt engine to tools/566-otel-span-receipt-verifier.html -- a human's browser-generated bundle and this tool's output interoperate on the exact same wire shape. It is categorised as a Execute tool in the Ainumbers Mcp Apps MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does otlp_span_receipt accept? +

otlp_span_receipt accepts 4 parameters: trace, bundle, service, run_chain_result. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on otlp_span_receipt? +

Register the Ainumbers Mcp Apps MCP server in PolicyLayer and add a rule for otlp_span_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 Ainumbers Mcp Apps. Nothing to install.

What risk level is otlp_span_receipt? +

otlp_span_receipt is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit otlp_span_receipt? +

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

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

otlp_span_receipt is provided by the Ainumbers Mcp Apps MCP server (postoaklabs/ainumbers-mcp-apps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ainumbers Mcp Apps, and thousands of servers like it.

This server

All 688 Ainumbers Mcp Apps tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →