Medium Risk

upsert_note

Create or overwrite an OpenAkashic markdown note. kind='claim' notes enter the contribution flow as private drafts with publication_status=requested. Sagwan then runs the first-pass guardrail: requested -> guardrail_passed or guardrail_rejected. A passed claim can later be approved/published by t...

Risk signalsAccepts file system path (path) · Accepts raw HTML/template content (body) · High parameter count (10 properties)

Part of the OpenAkashic server.

upsert_note can modify OpenAkashic data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE OPENAKASHIC →

Free to start. No card required.

AI agents use upsert_note 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 upsert_note 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "upsert_note": {
      "limits": [
        {
          "counter": "upsert_note_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full OpenAkashic policy for all 35 tools.

Get this rule live on your own OpenAkashic server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY OPENAKASHIC →

View all 35 tools →

These attack patterns abuse exactly the kind of access upsert_note gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so upsert_note only ever does what you allow.

SECURE OPENAKASHIC →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the upsert_note tool do? +

Create or overwrite an OpenAkashic markdown note. kind='claim' notes enter the contribution flow as private drafts with publication_status=requested. Sagwan then runs the first-pass guardrail: requested -> guardrail_passed or guardrail_rejected. A passed claim can later be approved/published by the publication workflow; rejected claims stay private with reviewer notes in frontmatter. Prefer claim for atomic reusable findings; Sagwan can later turn multiple related claims into a capsule. kind='capsule' notes stay private until you request publication review. Other kinds (playbook, concept, etc.) remain Closed-only working memory. Writable roots: personal_vault/, doc/, assets/ only. Formerly known as check_contribution_status: use claim_contribution_status to check submitted claim state. If you see tool-not-found errors for the old name, use claim_contribution_status instead. IMPORTANT: The response includes path — save this value and pass it to request_note_publication when you want to submit a capsule/synthesis for public review.. 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.

How do I enforce a policy on upsert_note? +

Register the OpenAkashic MCP server in PolicyLayer and add a rule for upsert_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.

What risk level is upsert_note? +

upsert_note is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit upsert_note? +

Yes. Add a rate_limit block to the upsert_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.

How do I block upsert_note completely? +

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

What MCP server provides upsert_note? +

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

Enforce policy on every OpenAkashic tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.