List all available blueprints for generate/destroy
AI agents call ember_list_blueprints to permanently remove resources in Ember Cli — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
An AI agent that decides to call ember_list_blueprints doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Ember Cli is gone — there is no undo for destructive operations.
Attacks that exploit this kind of access
List all available blueprints for generate/destroy. It is categorised as a Destructive tool in the Ember Cli MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ember Cli MCP server in PolicyLayer and add a rule for ember_list_blueprints: 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 Ember Cli. Nothing to install.
ember_list_blueprints 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 ember_list_blueprints 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 ember_list_blueprints. 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.
ember_list_blueprints is provided by the Ember Cli MCP server (stefanoamorelli/ember-cli-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.