get_workspace_decisions
[MAINTENANCE] Read-only: List workspace-level pinned decisions (active only by default, newest first).
This record as markdown: /tools/io-github-ajc3xc-meridian/get-workspace-decisions.md
What get_workspace_decisions does on Meridian
AI agents call get_workspace_decisions 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 |
|---|---|---|---|
include_superseded | boolean | — |
Parameters from the server's own tool schema.
Why get_workspace_decisions is rated Low
This is a straightforward data retrieval operation that queries and lists existing decisions. The 'read-only' designation, combined with list/retrieval semantics, clearly places it in the Read category. The maintenance flag and filtering options (active only by default, newest first) are presentation details that do not change the fundamental read-only nature.
From the tool's definition Description explicitly states 'Read-only: List workspace-level pinned decisions'. The tool retrieves and displays existing data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_workspace_decisions 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_decisions, this is the rule to start with:
get_workspace_decisions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Meridian, apply this rule, and every get_workspace_decisions call is checked against it from then on.
Questions about get_workspace_decisions
[MAINTENANCE] Read-only: List workspace-level pinned decisions (active only by default, newest first). It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.
get_workspace_decisions accepts 1 parameter: include_superseded. The full parameter table on this page comes from the server's own tool schema.
Register the Meridian MCP server in PolicyLayer and add a rule for get_workspace_decisions: 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.
get_workspace_decisions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_workspace_decisions 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.
Set action: deny in the PolicyLayer policy for get_workspace_decisions. 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.
get_workspace_decisions 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.
More on Meridian, and thousands of servers like it.
This server
Across the catalogue