register_run_artifact

SERVERMeridian SOURCE@meridianmcp/mcp

Medium RISK CLASS

Category Write

Parameters 72 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-ajc3xc-meridian/register-run-artifact.md

WHAT IT DOES

What register_run_artifact does on Meridian

AI agents use register_run_artifact 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
`run_id`	string	Yes
`project_id`	string	—
`session_id`	string	—
`content_hash`	string	—
`logical_path`	string	Yes	Project-relative path — never a machine-local absolute path.
`project_name`	string	—	Project name — an alternative to project_id; resolved to the id internally. project_id wins if both are given.
`artifact_role`	string	—

Parameters from the server's own tool schema.

RISK

Why register_run_artifact is rated Medium

An AI agent can call register_run_artifact faster than any human can review: one bad instruction and it creates or modifies resources in Meridian by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

register_run_artifact Rate-limited

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

FAQ

Questions about register_run_artifact

What does the register_run_artifact tool do? +

[SUPPORT] 3f6b8715 — register a project-RELATIVE artifact against a run. Rejects an absolute path (any shape capability_manifest recognizes, a bare leading '/', a drive letter, a UNC path, or a '..' traversal segment) or a secret-shaped value with {error}. Persistent-state disclosure: on hosted Meridian, supplied text and project/session metadata -- including task log entries, pinned decisions, sprint items, notes, handoff/goal state, and HITL queue items -- are sent to and stored in Meridian's service, in an isolated per-tenant Postgres database (Neon); self-hosted deployments keep the same categories in the configured local SQLite/Postgres database. This data is visible in the dashboard and API, and may resurface in later project context or handoffs. Notes and pinned decisions can be deleted individually; task log entries and sprint items can be deleted via the dashboard/API (not exposed as an agent-facing tool); HITL queue items and handoff state have no per-record delete. Full removal of any of this data is available via project or account deletion, 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 register_run_artifact accept? +

register_run_artifact accepts 7 parameters: run_id, project_id, session_id, content_hash, logical_path, project_name, artifact_role. Required: run_id, logical_path. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on register_run_artifact? +

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

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

Can I rate-limit register_run_artifact? +

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

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

register_run_artifact 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 235 Meridian tools →

Across the catalogue

team_manager_register_agents on Team Manager MCP → The MCP Attack Database →

Guides

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