New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_design_system_component

Delete a Design System component variant.

SERVEREnterprise-Multi-Agent-Engine SOURCEMojtaba-Dehghani/Enterprise-Multi-Agent-Engine
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/enterprise-multi-agent-engine/delete-design-system-component.md

What delete_design_system_component does on Enterprise-Multi-Agent-Engine

AI agents call delete_design_system_component to permanently remove resources in Enterprise-Multi-Agent-Engine, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_design_system_component is rated Critical

Irreversibly removes design system components; cannot be undone without restoration procedures.

From the tool's definition Delete a Design System component variant.

Questions about delete_design_system_component

What does the delete_design_system_component tool do? +

Delete a Design System component variant. It is categorised as a Destructive tool in the Enterprise-Multi-Agent-Engine MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_design_system_component? +

Register the Enterprise-Multi-Agent-Engine MCP server in PolicyLayer and add a rule for delete_design_system_component: 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 Enterprise-Multi-Agent-Engine. Nothing to install.

What risk level is delete_design_system_component? +

delete_design_system_component is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_design_system_component? +

Yes. Add a rate_limit block to the delete_design_system_component 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.

How do I block delete_design_system_component completely? +

Set action: deny in the PolicyLayer policy for delete_design_system_component. 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.

What MCP server provides delete_design_system_component? +

delete_design_system_component is provided by the Enterprise-Multi-Agent-Engine MCP server (Mojtaba-Dehghani/Enterprise-Multi-Agent-Engine). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Enterprise-Multi-Agent-Engine, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Enterprise-Multi-Agent-Engine's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.