Sync subscription plan features from the local database to the production database. DESTRUCTIVE: truncates subscription_plan_features on production. Will prompt for confirmation before proceeding.
AI agents call cli_deploy_sync_features to permanently remove resources in LaunchFrame MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool explicitly truncates a production database table, which is an irreversible operation. Syncing from local to production and truncating production data is a highly destructive action with a massive blast radius — it can wipe critical subscription feature configurations in the live environment. Even though it prompts for confirmation, an AI agent could auto-confirm, making this critical severity.
From the tool's definition DESTRUCTIVE: truncates subscription_plan_features on production
Attacks that exploit this kind of access
Sync subscription plan features from the local database to the production database. DESTRUCTIVE: truncates subscription_plan_features on production. Will prompt for confirmation before proceeding. It is categorised as a Destructive tool in the LaunchFrame MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the LaunchFrame MCP server in PolicyLayer and add a rule for cli_deploy_sync_features: 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 LaunchFrame MCP. Nothing to install.
cli_deploy_sync_features is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cli_deploy_sync_features 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.
Set action: deny in the PolicyLayer policy for cli_deploy_sync_features. 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.
cli_deploy_sync_features is provided by the LaunchFrame MCP server (launchframe-dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →