add_workspace_proposal

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/add-workspace-proposal.md

WHAT IT DOES

What add_workspace_proposal does on Meridian

AI agents use add_workspace_proposal 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
`body`	string	Yes	Full description of the insight or idea.
`tags`	string	—	Optional comma-separated tags.
`title`	string	Yes	Short idea title.

Parameters from the server's own tool schema.

RISK

Why add_workspace_proposal is rated Medium

The tool writes new persistent records to a workspace-level storage system but does not execute arbitrary code, delete data irreversibly, or move money. The severity is medium because misuse (e.g., flooding with spam proposals, storing sensitive data in proposals) could clutter the workspace and potentially expose metadata to human reviewers, but the impact is containable through human review gates and the…

From the tool's definition Tool creates new proposal records via 'add_workspace_proposal' that are stored persistently in state ('sent to and stored in Me[ridian]').

Risk signalsAccepts raw HTML/template content (body)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

add_workspace_proposal Rate-limited

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

FAQ

Questions about add_workspace_proposal

What does the add_workspace_proposal tool do? +

Capture a workspace-level flash of insight into the 'drawer of inspiration' — cross-project ideas that don't belong to any one project yet. Unlike sprint items these are NOT executor-claimable; they require a human to review and promote them. Proposals start at status='raw' and progress through an enforced lifecycle: raw → investigating → promoted|rejected. Use advance_proposal_status to move through the lifecycle; use promote_proposal to convert one into a real sprint item. 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 add_workspace_proposal accept? +

add_workspace_proposal accepts 3 parameters: body, tags, title. 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 add_workspace_proposal? +

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

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

Can I rate-limit add_workspace_proposal? +

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

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

add_workspace_proposal 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

add-tag on Kanban MCP Server →kb_add on Persistent Kb →add_video on Mcptube Vision → The MCP Attack Database →

Guides

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