// MCP TOOL REFERENCE

journal_recall

Retrieve recent session context and journeys. Call at START of sessions to remember the relationship.

Part of the Session Forge MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

// WHEN AI AGENTS USE THIS TOOL

AI agents invoke journal_recall to trigger processes or run actions in Session Forge. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

// WHY ENFORCE A POLICY ON JOURNAL_RECALL

journal_recall can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

// RECOMMENDED POLICY

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

session-forge.yaml

tools:
  journal_recall:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Session Forge policy for all 15 tools.

// DETAILS

Tool Name journal_recall

Category Execute

MCP Server Session Forge MCP Server

Risk Level High

// MORE SESSION FORGE TOOLS

Destructive data_manage Write profile_update Write session_checkpoint Write session_complete Write session_restore Read data_delete Read data_list Read dead_end_record

View all 15 tools →

// WHAT CAN GO WRONG

Agents calling execute-class tools like journal_recall have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER EXECUTE TOOLS ACROSS MCP SERVERS

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

Agent Passport System — Cryptographic Identity for AI Agents commerce_preflight Agent Passport System — Cryptographic Identity for AI Agents execute_with_context Agent Passport System — Cryptographic Identity for AI Agents gateway_execute_approval Agent Passport System — Cryptographic Identity for AI Agents governance_360 Agent Passport System — Cryptographic Identity for AI Agents parse_governance_block_html AgentClear — API Marketplace for AI Agents call_service

// IN CONTEXT OF HIGH RISK

journal_recall is one of the high-risk operations in Session Forge. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

// RELATED READING

// FAQ

What does the journal_recall tool do? +

Retrieve recent session context and journeys. Call at START of sessions to remember the relationship.. It is categorised as a Execute tool in the Session Forge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on journal_recall? +

Add a rule in your Intercept YAML policy under the tools section for journal_recall. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Session Forge MCP server.

What risk level is journal_recall? +

journal_recall is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit journal_recall? +

Yes. Add a rate_limit block to the journal_recall rule in your Intercept 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_recall completely? +

Set action: deny in the Intercept policy for journal_recall. 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_recall? +

journal_recall is provided by the Session Forge MCP server (session-forge). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

journal_recall

Enforce policies on Session Forge