Skip to main content
Glama
jgt87

Copilot Studio MCP

by jgt87
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Enable or edit managed environments

cs_admin_set_governance_config

Enable or disable managed environments and configure governance settings such as sharing limits, solution checker mode, and maker onboarding for a Power Platform environment.

Instructions

Turn managed environments on ('Standard') or off ('Basic') for an environment and set its governance options: sharing limits, solution checker mode, maker onboarding. Changes tenant governance: requires confirm: true. Runs 'pac admin set-governance-config' with the active pac auth profile. Mutates a live environment: requires confirm: true (a dry run otherwise).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNoWorking directory for pac (for project commands: the solution project folder)
confirmNoRequired to actually perform a change in a live environment. Without it the tool returns a dry run.
profileNopac auth profile to run as: the admin account for tenant commands. Defaults to CPS_ADMIN_PROFILE for admin commands and CPS_PAC_PROFILE otherwise, then the active profile. cs_init lists the profiles.
backgroundNoRun in the background and return a jobId immediately, for a command that takes longer than the client will wait. Poll cs_job_status.
environmentYesEnvironment id or URL
cloudFlowsModeNoSharing limit mode for solution cloud flows
timeoutSecondsNoDefault 600
cloudFlowsLimitNoHow many people makers may share solution cloud flows with
excludeAnalysisNoExclude this environment from the weekly usage digest
includeInsightsNoShow insights on the admin centre home page
protectionLevelYesStandard enables managed environments, Basic disables them
limitSharingModeNoSharing limit mode
makerOnboardingUrlNoMaker onboarding URL
disableGroupSharingNoDisable sharing with groups
maxLimitUserSharingNoHow many people makers may share canvas apps with
solutionCheckerModeNoSolution checker validation mode (None, Warn, Block)
checkerRuleOverridesNoSolution checker rule overrides
makerOnboardingMarkdownNoMaker onboarding markdown
suppressValidationEmailsNoDo not send validation emails

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.8
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.1.5

TDQS

B3.3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden. It usefully discloses that this mutates a live environment, that confirm: true is required, and that omitting it yields a dry run, plus which pac command runs. However it does not state what happens to unset governance options, whether changes are reversible, or what permissions the admin profile needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Core purpose is front-loaded and clear, but the description is redundant: 'requires confirm: true' is stated twice and the dry-run behavior is repeated. That duplicated warning costs space without adding information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 19-parameter tenant-governance mutation with no annotations and no output schema, the description covers purpose and the confirm gate adequately, and the schema handles parameters. It remains incomplete on sibling routing and on the effect of unspecified options, which matters for a broad mutation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all 19 parameters; baseline is 3. The description adds only light mapping (protectionLevel Standard/Basic, and the categories of governance options), not syntax or interaction details beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: turn managed environments on ('Standard') or off ('Basic') and set governance options (sharing limits, solution checker mode, maker onboarding). This clearly distinguishes it from sibling admin tools like cs_admin_update_tenant_settings or cs_admin_set_runtime_state.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states preconditions (confirm: true, tenant-wide scope) but gives no when-to-use guidance relative to siblings, nor any exclusions or alternative tools for adjacent governance tasks. An agent must infer context on its own.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools