get_insights
[SUPPORT] Read-only: List a project's strategic insights (newest first), optionally filtered by horizon (permanent|year|quarter). Review accumulated understanding before planning. permanent insights also appear automatically in get_planning_brief.
This record as markdown: /tools/io-github-ajc3xc-meridian/get-insights.md
What get_insights does on Meridian
AI agents call get_insights 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 |
|---|---|---|---|
horizon | string | — | Optional horizon filter. |
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.
Why get_insights is rated Low
get_insights retrieves and filters existing data (strategic insights) without creating, modifying, deleting, or executing any operations. It is a passive query operation that serves an informational purpose in task coordination. The low severity reflects minimal blast radius—misuse would only result in inappropriate information exposure, not data loss or unauthorized actions.
From the tool's definition Tool description explicitly states 'Read-only: List a project's strategic insights'. The verb 'List' and the modifier 'Read-only' are definitive indicators of a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_insights 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_insights, this is the rule to start with:
get_insights 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_insights call is checked against it from then on.
Questions about get_insights
[SUPPORT] Read-only: List a project's strategic insights (newest first), optionally filtered by horizon (permanent|year|quarter). Review accumulated understanding before planning. permanent insights also appear automatically in get_planning_brief. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.
get_insights accepts 3 parameters: horizon, project_id, project_name. 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_insights: 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_insights 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_insights 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_insights. 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_insights 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