update_workspace_settings

[MAINTENANCE] Update workspace-global default settings. Pass only the fields you want to change. hitl_auto_answer_default (bool) seeds new projects' HITL auto-answer behaviour; sprint_name_default (string) is the default sprint name; handoff_template (string) overrides the default full-mode handoff with a custom template — supports {{sprint}}, {{recent_tasks}}, {{decisions}}, {{north_star}}, {{version_goal}}, {{pending_items}}, {{notes}} placeholders. execution_mode_default ('autonomous'|'interactive', '' to clear) and code_intel_enabled_default (bool) are cascade defaults seeded onto NEW projects in this workspace (existing projects are unchanged). loop_enabled_default (bool) is the workspace default for /loop auto-continue that projects inherit when their loop_enabled is 'workspace'. tool_priority_map (object) sets a durable default MCP tool per semantic task category (e.g. {"code-reading": "Serena: find_symbol"}) — generalizes the per-item required_tool pin up one level; rendered as a HARD, unconditional directive in every /goal for matching pending items that have no item-level required_tool override. Pass {} to clear it. claim_verification_mode ('off'|'advisory'|'strict', '' to clear back to 'off') controls whether a PostToolUse hook re-checks claim_sprint_item/complete_sprint_item calls against live sprint-item state before trusting the calling session's own narration: 'off' = no check; 'advisory' = logs a warning on mismatch but never blocks; 'strict' = blocks the session on mismatch. Pass an empty string to revert a field to the server default. 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.

update_workspace_settings accepts 8 parameters: handoff_template, tool_priority_map, sprint_name_default, loop_enabled_default, execution_mode_default, claim_verification_mode, hitl_auto_answer_default, code_intel_enabled_default. 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 update_workspace_settings: 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.

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

Yes. Add a rate_limit block to the update_workspace_settings 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 update_workspace_settings. 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.

update_workspace_settings 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.