session_log · Recap MCP: Risk & Policy

WHAT IT DOES

What session_log does on Recap

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

WHY IT NEEDS A POLICY

Why session_log needs a policy

This tool creates a new session log entry in the project's markdown files. It writes data (session notes, decisions, next steps) but does not delete or overwrite existing data, execute code, or involve financial transactions. The blast radius is low — misuse could write incorrect or misleading session notes, but this is reversible and contained within local markdown files.

From the tool's definition 'Log a session entry for a project: what was worked on, decisions made, next steps'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

session_log Rate-limited

session_log 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": {
    "session_log": {
      "limits": [
        {
          "counter": "session_log_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 Recap, so you can run agents against it safely.

FAQ

Questions about session_log

What does the session_log tool do? +

Log a session entry for a project: what was worked on, decisions made, next steps. The core. It is categorised as a Write tool in the Recap MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on session_log? +

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

What risk level is session_log? +

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

Can I rate-limit session_log? +

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

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

session_log is provided by the Recap MCP server (shivam-singh-git/recap-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.