Read invinoveritas's PUBLIC, SIGNED, AUDITABLE verdict track record — the proof you can trust this verifier WITHOUT trusting us. Each entry is a signed Nostr event: recompute its event id and verify the schnorr signature against our published pubkey to confirm authorship + integrity; outcomes set...
Part of the Invinoveritas server.
Free to start. No card required.
AI agents call ledger to retrieve information from Invinoveritas 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 ledger 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.
{
"version": "1",
"default": "deny",
"tools": {
"ledger": {}
}
}See the full Invinoveritas policy for all 26 tools.
These attack patterns abuse exactly the kind of access ledger gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Read invinoveritas's PUBLIC, SIGNED, AUDITABLE verdict track record — the proof you can trust this verifier WITHOUT trusting us. Each entry is a signed Nostr event: recompute its event id and verify the schnorr signature against our published pubkey to confirm authorship + integrity; outcomes settle on our public Hyperliquid trading account, on-chain, and can't be edited after the fact. We publish our failures, not just our wins. Call with no args for the index, or pass entry to read one signed verdict. This is the agent-to-agent 'should I rely on this verifier?' primitive.. It is categorised as a Read tool in the Invinoveritas MCP Server, which means it retrieves data without modifying state.
Register the Invinoveritas MCP server in PolicyLayer and add a rule for ledger: 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 Invinoveritas. Nothing to install.
ledger is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ledger 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.
Set action: deny in the PolicyLayer policy for ledger. 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.
ledger is provided by the Invinoveritas MCP server (https://api.babyblueviper.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 26 Invinoveritas 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.