pin_workspace_decision

SERVERMeridian SOURCE@meridianmcp/mcp

Medium RISK CLASS

Category Write

Parameters 32 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/pin-workspace-decision.md

WHAT IT DOES

What pin_workspace_decision does on Meridian

AI agents use pin_workspace_decision 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
`body`	string	Yes
`title`	string	Yes
`category`	string	—

Parameters from the server's own tool schema.

RISK

Why pin_workspace_decision is rated Medium

The tool creates and persists workspace-level metadata that propagates globally across all projects and handoffs. While it modifies shared state reversibly (the description hints at deletion capability: 'Delete individual tasks, notes, or...'), it does not irreversibly destroy data, nor does it execute arbitrary code or transfer money.

From the tool's definition Tool 'pins' a workspace-level decision that is 'injected at the top of every project's context block + handoff' and explicitly states data is 'stored in Meridian's service' with persistence across sessions and visibility in 'dashboard/API and later project…

Risk signalsAccepts raw HTML/template content (body) · Bulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

pin_workspace_decision Rate-limited

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

FAQ

Questions about pin_workspace_decision

What does the pin_workspace_decision tool do? +

[MAINTENANCE] Pin a workspace-level decision that applies across ALL projects (shared architecture, org-wide standards). Injected at the top of every project's context block + handoff. category is free-text (STRATEGIC, TECHNICAL, ARCHITECTURAL, PRODUCT, ...). 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 pin_workspace_decision accept? +

pin_workspace_decision accepts 3 parameters: body, title, category. Required: body, title. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on pin_workspace_decision? +

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

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

Can I rate-limit pin_workspace_decision? +

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

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

pin_workspace_decision 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

team_manager_emit_decision on Team Manager MCP → The MCP Attack Database →

Guides

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