New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

anchor_stamp

Calls the anchor-suite MCP server (server-to-server, not the browser CORS-gated relay) to timestamp one execution_hash, or batch-anchor an array via anchor-suite's own anchor_batch (one upstream call per batch, RFC 6962 Merkle root anchored, per-hash merkle_inclusion returned), and shapes the res...

SERVERAinumbers Mcp Apps SOURCEpostoaklabs/ainumbers-mcp-apps
Low RISK CLASS
Category Read
Parameters 21 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/postoaklabs-ainumbers-mcp-apps/anchor-stamp.md

What anchor_stamp does on Ainumbers Mcp Apps

AI agents call anchor_stamp to retrieve information from Ainumbers Mcp Apps without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
authority string Defaults to whatever anchor-suite's own anchor_hash/anchor_batch default to today (currently sigstore for rfc3161-tst) -- this tool does not own or hardcode a p
execution_hash object Yes The execution_hash(es) to anchor.

Parameters from the server's own tool schema.

Why anchor_stamp is rated Low

Even though anchor_stamp only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsAdmin/system-level operation

Questions about anchor_stamp

What does the anchor_stamp tool do? +

Calls the anchor-suite MCP server (server-to-server, not the browser CORS-gated relay) to timestamp one execution_hash, or batch-anchor an array via anchor-suite's own anchor_batch (one upstream call per batch, RFC 6962 Merkle root anchored, per-hash merkle_inclusion returned), and shapes the result as literal OCG v0.7 section 20 anchor_bindings entries ready to append to an artifact. Success is only reported after this tool independently confirms anchored_hash (or, for a batch entry, merkle_inclusion.leaf) equals the caller-supplied hash -- it does not merely trust anchor-suite's response. On ANY failure -- anchor-suite unreachable, erroring, timing out, or an equality mismatch -- returns {ok:false, unanchored:true, reason} verbatim, never a fabricated binding. Caller-invoked only; not wired into any automatic per-artifact-emission path. It is categorised as a Read tool in the Ainumbers Mcp Apps MCP Server, which means it retrieves data without modifying state.

What parameters does anchor_stamp accept? +

anchor_stamp accepts 2 parameters: authority, execution_hash. Required: execution_hash. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on anchor_stamp? +

Register the Ainumbers Mcp Apps MCP server in PolicyLayer and add a rule for anchor_stamp: 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 anchor_stamp? +

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

Can I rate-limit anchor_stamp? +

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

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

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

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

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Ainumbers Mcp Apps's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.