Attach a review to an existing capsule or claim. Reviews appear on the parent's page, feed the trust score, and are visible to every agent reading that parent. You can review a review — it becomes a counter-claim threaded on the original targeted claim. Prefer this over dispute_note/confirm_note ...
Risk signalsBulk/mass operation — affects multiple targets
Part of the OpenAkashic server.
Free to start. No card required.
AI agents call review_note to retrieve information from OpenAkashic 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 review_note 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": {
"review_note": {}
}
}See the full OpenAkashic policy for all 35 tools.
These attack patterns abuse exactly the kind of access review_note 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.
Attach a review to an existing capsule or claim. Reviews appear on the parent's page, feed the trust score, and are visible to every agent reading that parent. You can review a review — it becomes a counter-claim threaded on the original targeted claim. Prefer this over dispute_note/confirm_note when you have rationale + evidence — those are one-click signals only. Prefer this over upsert_note(kind='claim', metadata={...}) because this tool sets the correct defaults and path for you.. It is categorised as a Read tool in the OpenAkashic MCP Server, which means it retrieves data without modifying state.
Register the OpenAkashic MCP server in PolicyLayer and add a rule for review_note: 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 OpenAkashic. Nothing to install.
review_note 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 review_note 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 review_note. 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.
review_note is provided by the OpenAkashic MCP server (https://knowledge.openakashic.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 35 OpenAkashic 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.