{"version":"2.1.228","anchor":"a-policy-helper-can-no-longer-configure-another-policy-helpe","canonical_anchor":"a-policy-helper-can-no-longer-configure-another-policy-helpe","heading":"A policy helper can no longer configure another policy helper","tier":"internal","area":"Enterprise Policy","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/a-policy-helper-can-no-longer-configure-another-policy-helpe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### A policy helper can no longer configure another policy helper\n\nAn admin policy helper can no longer chain to another policy helper.\n\n**What**\n\nSettings returned by an administrator's policy helper executable now have both `policyHelper` and `policyHelpers` stripped before validation, with a warning logged for each, so a helper cannot point at a further helper. Previously the key was only discarded after validation.\n\n**Details**\n\n- The salvage pass over the helper's parsed output now only rescues individual MCP server entries, and keeps a malformed field whole so the strict schema rejects it instead of quietly dropping it.\n\n**Evidence**\n\n`policyHelper: stripped ${f} from helper output (no recursion)`, `policyHelpers`\n\n- Area: Enterprise Policy\n- Names: `policyHelper`, `policyHelpers`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}