distill_journal · Kontexta MCP: Risk & Policy

WHAT IT DOES

What distill_journal does on Kontexta

AI agents use distill_journal 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 distill_journal needs a policy

The tool reads raw events and then writes structured markdown entries while advancing a persistent high-water mark. This is a Write operation: it creates or modifies data (journal entries and state markers) but is described as idempotent, meaning re-runs don't compound effects. It doesn't execute arbitrary code, delete data, or involve financial transactions.

From the tool's definition 'write mechanical markdown entries, advance high-water' — creates/modifies markdown journal entries and updates a high-water mark state

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

distill_journal Rate-limited

distill_journal 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": {
    "distill_journal": {
      "limits": [
        {
          "counter": "distill_journal_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 distill_journal

What does the distill_journal tool do? +

Run the distillation pipeline: read raw events since the high-water mark, group by topic, write mechanical markdown entries, advance high-water. Idempotent. 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 distill_journal? +

Register the Kontexta MCP server in PolicyLayer and add a rule for distill_journal: 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 distill_journal? +

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

Can I rate-limit distill_journal? +

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

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

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