get_session_brief

SERVERMeridian SOURCE@meridianmcp/mcp

Low RISK CLASS

Category Read

Parameters 40 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ajc3xc-meridian/get-session-brief.md

WHAT IT DOES

What get_session_brief does on Meridian

AI agents call get_session_brief 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
`role`	string	—	Tailors the brief. 'worker'=sprint+tasks only; 'executor'=adds version-scoped pending items, this session's file claims, and decisions code-anchored to them (pa
`project_id`	string	—
`session_id`	string	—	Caller session id — enables session-scratchpad notes, board-change detection, and (role='executor') file-claim + version scoping.
`project_name`	string	—	Project name — an alternative to project_id; resolved to the id internally. project_id wins if both are given.

Parameters from the server's own tool schema.

RISK

Why get_session_brief is rated Low

This tool retrieves and queries session state, project summaries, and task history without side effects. The read-only designation and the operations described (returning/reading data) clearly place this in the Read category. Severity is low because it only accesses informational data about the session with no ability to modify, execute, or affect external systems.

From the tool's definition Tool description explicitly states 'Read-only' and describes retrieval operations: 'returns session, tasks, decisions, and recent commits' with no modification, deletion, or execution capabilities.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_session_brief 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_brief, this is the rule to start with:

get_session_brief Allowed

get_session_brief is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_session_brief": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Meridian, apply this rule, and every get_session_brief call is checked against it from then on.

FAQ

Questions about get_session_brief

What does the get_session_brief tool do? +

[SUPPORT] Read-only: Call this FIRST for project summaries or to see what a session did — returns session, tasks, decisions, and recent commits in one call. Replaces the start_session + get_context_block two-call pattern for worker/automation sessions. Returns sprint focus, pending sprint items, recent tasks, any blocking failures, and pending HITL requests in a compact XML envelope (<500 tokens). It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.

What parameters does get_session_brief accept? +

get_session_brief accepts 4 parameters: role, project_id, session_id, project_name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_session_brief? +

Register the Meridian MCP server in PolicyLayer and add a rule for get_session_brief: 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.

What risk level is get_session_brief? +

get_session_brief is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_session_brief? +

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

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

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

KEEP EXPLORING

More on Meridian, and thousands of servers like it.

This server

All 175 Meridian tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →