delete_brand_kit

Delete a brand kit.

SERVEREasyBits SOURCE@easybits.cloud/mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/cloud-easybits-easybits/delete-brand-kit.md

WHAT IT DOES

What delete_brand_kit does on EasyBits

AI agents call delete_brand_kit to permanently remove resources in EasyBits, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why delete_brand_kit is rated Critical

Irreversibly removes brand kit data without recovery option.

From the tool's definition Delete a brand kit.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_brand_kit safely

PolicyLayer is an MCP gateway: it sits between your AI agents and EasyBits, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_brand_kit, this is the rule to start with:

delete_brand_kit Hidden

delete_brand_kit is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_brand_kit"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect EasyBits, apply this rule, and every delete_brand_kit call is checked against it from then on.

FAQ

Questions about delete_brand_kit

What does the delete_brand_kit tool do? +

Delete a brand kit. It is categorised as a Destructive tool in the EasyBits 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_brand_kit? +

Register the EasyBits MCP server in PolicyLayer and add a rule for delete_brand_kit: 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 EasyBits. Nothing to install.

What risk level is delete_brand_kit? +

delete_brand_kit 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_brand_kit? +

Yes. Add a rate_limit block to the delete_brand_kit 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_brand_kit completely? +

Set action: deny in the PolicyLayer policy for delete_brand_kit. 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_brand_kit? +

delete_brand_kit is provided by the EasyBits MCP server (@easybits.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on EasyBits, and thousands of servers like it.

This server

All 273 EasyBits tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern infrastructure agents →Blast radius →Tool call approval →