get_session_activity
[MAINTENANCE] Read-only: Return the raw MCP-tool-call heartbeat feed for the given executor session — a ring-buffer of the last tool calls (newest first, up to 50 entries). Populated automatically by the MCP dispatcher on every executor tool call, no log_task() needed. Use this to check whether a...
This record as markdown: /tools/io-github-ajc3xc-meridian/get-session-activity.md
What get_session_activity does on Meridian
AI agents call get_session_activity 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 |
|---|---|---|---|
limit | integer | — | Max entries to return (default 20, max 50). |
session_id | string | Yes |
Parameters from the server's own tool schema.
Why get_session_activity is rated Low
This tool only reads historical heartbeat/activity data from a ring-buffer of past tool calls. It has no side effects, creates no data, modifies nothing, and executes no code. The explicit 'Read-only' designation and monitoring/diagnostic purpose (checking executor status) confirm it belongs in the Read category with low severity.
From the tool's definition Tool is explicitly marked '[MAINTENANCE] Read-only' and described as 'Return the raw MCP-tool-call heartbeat feed' — it retrieves and queries activity logs without modification.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs get_session_activity 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_activity, this is the rule to start with:
get_session_activity 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_activity call is checked against it from then on.
Questions about get_session_activity
[MAINTENANCE] Read-only: Return the raw MCP-tool-call heartbeat feed for the given executor session — a ring-buffer of the last tool calls (newest first, up to 50 entries). Populated automatically by the MCP dispatcher on every executor tool call, no log_task() needed. Use this to check whether an executor is still running when task_count is 0. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.
get_session_activity accepts 2 parameters: limit, session_id. 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_activity: 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_activity 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_activity 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_activity. 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_activity 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