get_session_log
[MAINTENANCE] Read-only: Return the full task log for the given session. Returns every log_task description logged during the session (transcript/task_count) PLUS a recent_activity ring-buffer of the last tool calls the executor made — even before log_task() was called. Use recent_activity to che...
This record as markdown: /tools/io-github-ajc3xc-meridian/get-session-log.md
What get_session_log does on Meridian
AI agents call get_session_log to retrieve information from Meridian without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
session_id | string | Yes | |
activity_limit | integer | — | Max recent_activity entries to return (default 20, max 50). |
Parameters from the server's own tool schema.
Why get_session_log is rated Low
This tool retrieves session logs and activity history for review and monitoring purposes. It has no side effects—it only reads and returns existing data. While the log may contain sensitive information about session activity, the tool itself performs no destructive, write, execute, or financial operations.
From the tool's definition Tool description explicitly states 'Read-only: Return the full task log' and 'retrieves...task log...log_task description...tool calls.' No modification, deletion, or execution of external operations occurs.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs get_session_log safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meridian, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_session_log, this is the rule to start with:
get_session_log is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Meridian, apply this rule, and every get_session_log call is checked against it from then on.
Questions about get_session_log
[MAINTENANCE] Read-only: Return the full task log for the given session. Returns every log_task description logged during the session (transcript/task_count) PLUS a recent_activity ring-buffer of the last tool calls the executor made — even before log_task() was called. Use recent_activity to check signs of life in a running executor. Useful for post-session review, handoff, or remote planner polling. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.
get_session_log accepts 2 parameters: session_id, activity_limit. Required: session_id. The full parameter table on this page comes from the server's own tool schema.
Register the Meridian MCP server in PolicyLayer and add a rule for get_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 Meridian. Nothing to install.
get_session_log is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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.
Set action: deny in the PolicyLayer policy for get_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.
get_session_log is provided by the Meridian MCP server (@meridianmcp/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meridian, and thousands of servers like it.
This server
Across the catalogue