journal_note · Kontexta MCP: Risk & Policy

WHAT IT DOES

What journal_note does on Kontexta

AI agents use journal_note to create or update resources in Kontexta — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kontexta environment.

WHY IT NEEDS A POLICY

Why journal_note needs a policy

This tool writes a journal/note entry into the project knowledge vault. It creates new data (a note) but does so reversibly — notes can be deleted or overwritten. No code execution, financial action, or irreversible destruction is implied. Severity is low because misuse would at worst add unwanted notes to the project journal.

From the tool's definition Record a free-form decision/abandonment/observation note in the current project

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

journal_note Rate-limited

journal_note stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "journal_note": {
      "limits": [
        {
          "counter": "journal_note_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Kontexta, so you can run agents against it safely.

FAQ

Questions about journal_note

What does the journal_note tool do? +

Record a free-form decision/abandonment/observation note in the current project. It is categorised as a Write tool in the Kontexta MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on journal_note? +

Register the Kontexta MCP server in PolicyLayer and add a rule for journal_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 Kontexta. Nothing to install.

What risk level is journal_note? +

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

Can I rate-limit journal_note? +

Yes. Add a rate_limit block to the journal_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 journal_note completely? +

Set action: deny in the PolicyLayer policy for journal_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 journal_note? +

journal_note is provided by the Kontexta MCP server (safiyu/kontexta). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.