Critical-risk tools in ConfigCat
12 of the 72 tools in ConfigCat are classified as critical risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.
Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.
Tools at critical risk
-
delete-configDestructive 5/5Delete a config and all its feature flags
-
delete-environmentDestructive 5/5Delete an environment
-
delete-integrationDestructive 4/5Delete an integration
-
delete-invitationDestructive 3/5Cancel a pending invitation
-
delete-organization-memberDestructive 5/5Remove a member from the organisation
-
delete-permission-groupDestructive 5/5Delete a permission group
-
delete-productDestructive 5/5Delete a product and all its configuration
-
delete-product-memberDestructive 5/5Remove a member from a product
-
delete-segmentDestructive 4/5Delete a user segment
-
delete-settingDestructive 5/5Delete a feature flag permanently
-
delete-tagDestructive 3/5Delete a tag
-
delete-webhookDestructive 3/5Delete a webhook
Attacks that target this class
Critical-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.
More on ConfigCat
Enforce policy on ConfigCat
One command generates a policy scaffold for every server in your MCP config.
npx -y @policylayer/intercept init