journal_intent · Kontexta MCP: Risk & Policy

WHAT IT DOES

What journal_intent does on Kontexta

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

This tool creates a persistent record (write operation) of a topic or intent change. It does not execute code, delete data, or involve finances. The blast radius is low since it only logs metadata about conversation direction into the knowledge vault.

From the tool's definition 'Record a topic/intent pivot' — writes/stores a journal entry about a user's redirected intent

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

journal_intent Rate-limited

journal_intent 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_intent": {
      "limits": [
        {
          "counter": "journal_intent_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_intent

What does the journal_intent tool do? +

Record a topic/intent pivot. Use when the user redirects what you. 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_intent? +

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

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

Can I rate-limit journal_intent? +

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

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

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