{"version":"2.1.85","anchor":"enterprise-plugin-policy-enforcement","canonical_anchor":"enterprise-plugin-policy-enforcement","heading":"Enterprise Plugin Policy Enforcement","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.85\/e\/enterprise-plugin-policy-enforcement","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.85","markdown":"### Enterprise Plugin Policy Enforcement\n\n**What**\n\nOrganization administrators can now block specific plugins via enterprise policy, preventing installation and enablement.\n\n**Details**\n\n- Plugins can be blocked directly: \"Plugin {name} is blocked by your organization's policy and cannot be installed\"\n- Plugin dependencies can be blocked: \"Cannot install {name}: dependency {dep} is blocked by your organization's policy\"\n- Enabled plugins can be blocked: \"Plugin {name} is blocked by your organization's policy and cannot be enabled\"\n- MCP server blocking now shows explicit warnings: \"Warning: MCP server(s) blocked by enterprise policy: {names}\"\n- Claude.ai MCP servers also show warnings when blocked: \"Warning: claude.ai MCP server(s) blocked by enterprise policy: {names}\"\n- Terminology standardized from \"managed policy\" to \"enterprise policy\"\n\n**Evidence**\n\nPlugin blocking messages (search for `\"blocked by your organization's policy\"`)"}