get_workspace_proposals

SERVERMeridian SOURCE@meridianmcp/mcp

Low RISK CLASS

Category Read

Parameters 40 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ajc3xc-meridian/get-workspace-proposals.md

WHAT IT DOES

What get_workspace_proposals does on Meridian

AI agents call get_workspace_proposals to retrieve information from Meridian without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`tag`	string	—	Substring filter on tags.
`limit`	integer	—	Maximum proposals to return (default 20, clamped to 1..100).
`offset`	integer	—	Zero-based pagination offset (default 0).
`status`	string	—	Filter to proposals in this status. Defaults to raw+investigating ('live') when omitted; use 'all' for every status.

Parameters from the server's own tool schema.

RISK

Why get_workspace_proposals is rated Low

This tool performs data retrieval with filtering and pagination—classic read-only operations with no side effects. It lists existing workspace proposals without modification. The low severity reflects minimal blast radius; misuse would only expose proposal data already stored in the system.

From the tool's definition Tool description explicitly states 'Read-only: List a bounded page of workspace proposals' with filtering and pagination parameters (status, tag substring, offset). No write, delete, or execute operations are mentioned.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_workspace_proposals Allowed

get_workspace_proposals is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_workspace_proposals": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about get_workspace_proposals

What does the get_workspace_proposals tool do? +

[SUPPORT] Read-only: List a bounded page of workspace proposals (human-authored flashes of insight), newest first. When status is omitted, defaults to 'live' proposals only (raw + investigating) — terminal proposals (promoted/rejected) are excluded so the default view reflects what's actually still open. Pass status='all' to fetch every status, or an explicit status (including promoted/rejected) to filter to just that one. Optional tag substring filter. Pagination defaults to 20 rows (maximum 100); pass offset to fetch the next page. 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 Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.

What parameters does get_workspace_proposals accept? +

get_workspace_proposals accepts 4 parameters: tag, limit, offset, status. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_workspace_proposals? +

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

get_workspace_proposals is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_workspace_proposals? +

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

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

get_workspace_proposals 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →