updateOrgFeatureFlags

SERVERStable Baseline SOURCEhttps://api.stablebaseline.io/functions/v1/cloud-serve/mcp

Medium RISK CLASS

Category Write

Parameters 121 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-stablebaseline-sb/updateorgfeatureflags.md

WHAT IT DOES

What updateOrgFeatureFlags does on Stable Baseline

AI agents use updateOrgFeatureFlags to create or update resources in Stable Baseline, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Stable Baseline environment.

Parameter	Type	Required	Description
`plans`	boolean	—	Plans, phases, tasks and dependencies.
`agents`	boolean	—	Agents, with their duties and their connectors.
`own_ai`	boolean	—	The organisation's own AI provider. Off: its AI work runs on Stable Baseline's AI.
`databases`	boolean	—	Databases: tables, views, dashboards, imports and record links.
`documents`	boolean	—	Living documents, folders and diagrams.
`compliance`	boolean	—	Compliance readiness tracking.
`improvements`	boolean	—	The improvements and risk register.
`time_tracking`	boolean	—	Time tracking: timers and time entries on tasks, improvements and tables. Needs databases on.
`meeting_scribe`	boolean	—	The live meeting capture bot.
`time_approvals`	boolean	—	Time approvals: weeks submitted for a manager's or an admin's approval. Needs time tracking on.
`knowledge_graph`	boolean	—	The company brain across the workspace.
`organisation_id`	string	Yes

Parameters from the server's own tool schema.

RISK

Why updateOrgFeatureFlags is rated Medium

An AI agent can call updateOrgFeatureFlags faster than any human can review: one bad instruction and it creates or modifies resources in Stable Baseline by the hundred, each call as confident as the last.

Risk signalsHigh parameter count (14 properties) · Admin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs updateOrgFeatureFlags safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Stable Baseline, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For updateOrgFeatureFlags, this is the rule to start with:

updateOrgFeatureFlags Rate-limited

updateOrgFeatureFlags 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": {
    "updateOrgFeatureFlags": {
      "limits": [
        {
          "counter": "updateorgfeatureflags_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 Stable Baseline, apply this rule, and every updateOrgFeatureFlags call is checked against it from then on.

FAQ

Questions about updateOrgFeatureFlags

What does the updateOrgFeatureFlags tool do? +

Switch organisation modules on or off, one true or false a module: documents, plans, improvements, knowledge_graph, compliance, meeting_scribe, agents, time_tracking, time_approvals, databases, database_public_forms, customer_managed_keys, own_ai. getOrgSettings returns each module's current state. A module can be switched ON only when it is available to the organisation: its plan includes it (for example meeting_scribe needs Plus, Pro or Enterprise), or Stable Baseline made it available. Switching OFF is always allowed (customer_managed_keys excepted while the key is in use). A module that is off is off everywhere: its app pages are hidden, its tools are not offered, its actions are refused, and its background work pauses until it is on again. Nothing is deleted. database_public_forms needs databases on to take effect. Auth: can_admin_org + org owner or admin. Rate limit 30/min. It is categorised as a Write tool in the Stable Baseline MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does updateOrgFeatureFlags accept? +

updateOrgFeatureFlags accepts 12 parameters: plans, agents, own_ai, databases, documents, compliance, improvements, time_tracking, meeting_scribe, time_approvals, knowledge_graph, organisation_id. Required: organisation_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on updateOrgFeatureFlags? +

Register the Stable Baseline MCP server in PolicyLayer and add a rule for updateOrgFeatureFlags: 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 Stable Baseline. Nothing to install.

What risk level is updateOrgFeatureFlags? +

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

Can I rate-limit updateOrgFeatureFlags? +

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

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

updateOrgFeatureFlags is provided by the Stable Baseline MCP server (https://api.stablebaseline.io/functions/v1/cloud-serve/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Stable Baseline, and thousands of servers like it.

This server

All 222 Stable Baseline tools →

Across the catalogue

The MCP Attack Database →

Guides

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