Critical Risk →

cb_delete_asset

Remove um asset do Content Builder do SFMC pelo ID.

Part of the Ljit Mcp Sfmc server.

cb_delete_asset can permanently delete data in Ljit Mcp Sfmc, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE LJIT MCP SFMC →

Free to start. No card required.

AI agents may call cb_delete_asset to permanently remove or destroy resources in Ljit Mcp Sfmc. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call cb_delete_asset in a loop, permanently destroying resources in Ljit Mcp Sfmc. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "cb_delete_asset"
  ]
}

See the full Ljit Mcp Sfmc policy for all 40 tools.

Get this rule live on your own Ljit Mcp Sfmc server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY LJIT MCP SFMC →

View all 40 tools →

These attack patterns abuse exactly the kind of access cb_delete_asset gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so cb_delete_asset only ever does what you allow.

SECURE LJIT MCP SFMC →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the cb_delete_asset tool do? +

Remove um asset do Content Builder do SFMC pelo ID.. It is categorised as a Destructive tool in the Ljit Mcp Sfmc 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 cb_delete_asset? +

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

What risk level is cb_delete_asset? +

cb_delete_asset 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 cb_delete_asset? +

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

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

cb_delete_asset is provided by the Ljit Mcp Sfmc MCP server (ljit-mcp-sfmc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Ljit Mcp Sfmc tool call.

Deterministic rules across all 40 Ljit Mcp Sfmc tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.