store_finding

SERVERMeridian SOURCE@meridianmcp/mcp

Medium RISK CLASS

Category Write

Parameters 71 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ajc3xc-meridian/store-finding.md

WHAT IT DOES

What store_finding does on Meridian

AI agents use store_finding to create or update resources in Meridian, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meridian environment.

Parameter	Type	Required	Description
`key`	string	—	Optional bucket/topic for scoped retrieval (e.g. a subsystem name).
`title`	string	—	Optional short title.
`content`	string	Yes	The finding body.
`task_id`	string	—	Optional task this finding belongs to.
`project_id`	string	—
`session_id`	string	—	Optional writing session.
`project_name`	string	—	Project name — an alternative to project_id.

Parameters from the server's own tool schema.

RISK

Why store_finding is rated Medium

This tool writes data to a persistent store (session_findings table), creating or updating records that survive session boundaries. It is reversible in nature (data can be overwritten or deleted) and does not execute code, delete irreversibly, or involve financial operations.

From the tool's definition persist a per-task intermediate result to the session_findings table so it survives session boundaries... lightweight key→content store for agent-to-agent handoff of intermediate work

Risk signalsAccepts raw HTML/template content (content)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

store_finding Rate-limited

store_finding stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "store_finding": {
      "limits": [
        {
          "counter": "store_finding_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about store_finding

What does the store_finding tool do? +

[MAINTENANCE] PARALLEL COORDINATION (c35370cc): persist a per-task intermediate result to the session_findings table so it survives session boundaries. Parallel reader agents write findings; an orchestrator or writer agent reads them via get_findings. Unlike save_finding (which creates a research note), this is a lightweight key→content store for agent-to-agent handoff of intermediate work. Persistent-state disclosure: on hosted Meridian, supplied text and project/session metadata are sent to and stored in Meridian's service; self-hosted deployments keep them in the configured local SQLite/Postgres database. This data is visible in the dashboard/API and later project context or handoffs. Delete individual tasks, notes, or decisions where supported, or delete the project/account using the documented controls. Do not include secrets. It is categorised as a Write tool in the Meridian MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does store_finding accept? +

store_finding accepts 7 parameters: key, title, content, task_id, project_id, session_id, project_name. Required: content. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on store_finding? +

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

store_finding is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit store_finding? +

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

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

store_finding 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

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →