delete_site_utms

Delete UTM links by id.

SERVERWebcake Storefront SOURCEwebcake-storefront-mcp
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/webcake-storefront/delete-site-utms.md

What delete_site_utms does on Webcake Storefront

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

Why delete_site_utms is rated Critical

The tool performs an irreversible deletion operation on UTM (tracking) links. This fits the Destructive category because the action cannot be undone and removes data permanently. Severity is high because while UTM data loss affects analytics and marketing metrics rather than core business data, it can have significant operational impact on campaign tracking and reporting.

From the tool's definition Tool name explicitly states 'delete' and description confirms 'Delete UTM links by id' — this irreversibly removes tracking data.

Questions about delete_site_utms

What does the delete_site_utms tool do? +

Delete UTM links by id. It is categorised as a Destructive tool in the Webcake Storefront 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_site_utms? +

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

What risk level is delete_site_utms? +

delete_site_utms 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_site_utms? +

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

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

delete_site_utms is provided by the Webcake Storefront MCP server (webcake-storefront-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Webcake Storefront, 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 Webcake Storefront'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.