capture_research_finding

SERVERMeridian SOURCE@meridianmcp/mcp

Medium RISK CLASS

Category Write

Parameters 52 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/capture-research-finding.md

WHAT IT DOES

What capture_research_finding does on Meridian

AI agents use capture_research_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
`url`	string	Yes	Source URL of the web page or paper.
`summary`	string	Yes	Your summary of the finding (markdown).
`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.
`related_decision_id`	string	—	Optional pinned-decision id to link the finding to.

Parameters from the server's own tool schema.

RISK

Why capture_research_finding is rated Medium

The tool writes (creates) a new note/artifact by saving a research finding into persistent storage (hosted service or local database). It does not delete, execute code, or involve finances. The blast radius of misuse is low — worst case it pollutes the note/artifact store with spurious entries.

From the tool's definition 'save a finding from a URL as an addressable note with the source link' and 'Turns web-search results into durable Meridian artifacts' — creates/persists new records in the database

Risk signalsAccepts URL/endpoint input (url) · Bulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

capture_research_finding Rate-limited

capture_research_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": {
    "capture_research_finding": {
      "limits": [
        {
          "counter": "capture_research_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 capture_research_finding call is checked against it from then on.

FAQ

Questions about capture_research_finding

What does the capture_research_finding tool do? +

[SUPPORT] Inline capture for web/paper research during planning: save a finding from a URL as an addressable note with the source link, optionally linked to a decision. A research-shaped wrapper over save_finding — arXiv URLs are tagged source_type=arxiv automatically, everything else as web. Turns web-search results into durable Meridian artifacts instead of evaporating. 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 capture_research_finding accept? +

capture_research_finding accepts 5 parameters: url, summary, project_id, project_name, related_decision_id. Required: url, summary. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on capture_research_finding? +

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

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

Can I rate-limit capture_research_finding? +

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

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

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