get_workspace_settings
[MAINTENANCE] Read-only: Read workspace-global default settings (applies across ALL projects in this workspace): hitl_auto_answer_default and sprint_name_default. Returns the singleton settings row.
This record as markdown: /tools/io-github-ajc3xc-meridian/get-workspace-settings.md
What get_workspace_settings does on Meridian
AI agents call get_workspace_settings 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.
Why get_workspace_settings is rated Low
This tool only retrieves configuration data (hitl_auto_answer_default and sprint_name_default settings) from a singleton settings row. It performs no modifications, deletions, or external operations. The read-only designation and query-only nature clearly place it in the Read category. The blast radius is minimal—knowledge of default workspace settings poses no direct security or operational risk.
From the tool's definition Tool description explicitly states 'Read-only' and describes reading 'workspace-global default settings' which are configuration values with no side effects.
Attacks that exploit this kind of access
The rule that runs get_workspace_settings 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_settings, this is the rule to start with:
get_workspace_settings 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_settings call is checked against it from then on.
Questions about get_workspace_settings
[MAINTENANCE] Read-only: Read workspace-global default settings (applies across ALL projects in this workspace): hitl_auto_answer_default and sprint_name_default. Returns the singleton settings row. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.
Register the Meridian MCP server in PolicyLayer and add a rule for get_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.
get_workspace_settings 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_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 get_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.
get_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.
More on Meridian, and thousands of servers like it.
This server
Across the catalogue