get_context_block

SERVERMeridian SOURCE@meridianmcp/mcp

Low RISK CLASS

Category Read

Parameters 30 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-context-block.md

WHAT IT DOES

What get_context_block does on Meridian

AI agents call get_context_block 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
`mode`	string	—
`project_id`	string	—
`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_context_block is rated Low

This tool purely retrieves and formats existing project metadata (north star, sprint, tasks, decisions, sessions) for display to AI clients. It has no capacity to create, modify, delete, or execute operations—it only queries and returns data in a structured XML format. The explicit 'Read-only' designation confirms it belongs in the Read category.

From the tool's definition Tool description explicitly states 'Read-only: Return a compact project context block' and the operation retrieves project context without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_context_block Allowed

get_context_block 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_context_block": {}
  }
}

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_context_block call is checked against it from then on.

FAQ

Questions about get_context_block

What does the get_context_block tool do? +

[SUPPORT] Read-only: Return a compact project context block (north star, sprint, pending sprint items, recent tasks, recent decisions, active sessions) wrapped in a <meridian_context project_id="..." mode="..."> XML envelope for structured parsing by AI clients (v2.5+). The 'text' field in the response contains the XML-wrapped content. mode='full' (default) for Code Handoff into a fresh Claude Code session; mode='chat' for a shorter paste into a new claude.ai conversation. The HTTP route /projects/{id}/context-block returns the same content as unwrapped plain text. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.

What parameters does get_context_block accept? +

get_context_block accepts 3 parameters: mode, project_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_context_block? +

Register the Meridian MCP server in PolicyLayer and add a rule for get_context_block: 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_context_block? +

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

Can I rate-limit get_context_block? +

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

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

get_context_block 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 →