6 tools. 1 can modify or destroy data without limits.
1 write tool that can modify data. Rate limits recommended.
Last updated:
Free to start. No card required.
Full per-tool breakdown → Model it in the token calculator →
Write operations (issue_receipt) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
{
"issue_receipt": {
"limits": [
{
"counter": "issue_receipt_per_hour",
"window": "hour",
"max": 30,
"scope": "grant"
}
]
}
} Prevents bulk unintended modifications from agents caught in loops.
{
"get_proof_latest": {
"limits": [
{
"counter": "get_proof_latest_per_minute",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
} Controls API costs and prevents retry loops from exhausting upstream rate limits.
The PaymentOracle — Verifiable Multi-Rail Payment Receipts server has 1 write tools including issue_receipt. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach PaymentOracle — Verifiable Multi-Rail Payment Receipts.
6 tools across 2 categories: Read, Write. 5 are read-only. 1 can modify, create, or delete data.
Register the PaymentOracle — Verifiable Multi-Rail Payment Receipts MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.
Deterministic rules across all 6 PaymentOracle — Verifiable Multi-Rail Payment Receipts 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.