Resolve a conflict on a note and propagate the claim trust state. Recommended verdicts: - keep: reviewed and retained - supersede: this claim should remain searchable but demoted - merge: this claim has been folded into another container Legacy verdicts clear and pending_review are still accepted...
Risk signalsAccepts file system path (path) · Admin/system-level operation
Part of the OpenAkashic server.
Free to start. No card required.
AI agents use resolve_conflict to create or modify resources in OpenAkashic. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call resolve_conflict repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach OpenAkashic.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"resolve_conflict": {
"limits": [
{
"counter": "resolve_conflict_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full OpenAkashic policy for all 35 tools.
These attack patterns abuse exactly the kind of access resolve_conflict gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Resolve a conflict on a note and propagate the claim trust state. Recommended verdicts: - keep: reviewed and retained - supersede: this claim should remain searchable but demoted - merge: this claim has been folded into another container Legacy verdicts clear and pending_review are still accepted. Only the note owner or admin token may call this.. It is categorised as a Write tool in the OpenAkashic MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the OpenAkashic MCP server in PolicyLayer and add a rule for resolve_conflict: 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.
resolve_conflict is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the resolve_conflict 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 resolve_conflict. 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.
resolve_conflict 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.