Critical Risk →

delete_ad_tag

Delete an ad tag.

Part of the Zype Com server.

delete_ad_tag can permanently delete data in Zype Com, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE ZYPE COM →

Free to start. No card required.

AI agents may call delete_ad_tag to permanently remove or destroy resources in Zype Com. 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 delete_ad_tag in a loop, permanently destroying resources in Zype Com. 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": [
    "delete_ad_tag"
  ]
}

See the full Zype Com policy for all 76 tools.

Get this rule live on your own Zype Com server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY ZYPE COM →

View all 76 tools →

These attack patterns abuse exactly the kind of access delete_ad_tag 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 delete_ad_tag only ever does what you allow.

SECURE ZYPE COM →

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

What does the delete_ad_tag tool do? +

Delete an ad tag.. It is categorised as a Destructive tool in the Zype Com 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_ad_tag? +

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

What risk level is delete_ad_tag? +

delete_ad_tag 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_ad_tag? +

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

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

delete_ad_tag is provided by the Zype Com MCP server (@zype-com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Zype Com tool call.

Deterministic rules across all 76 Zype Com 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.