delete_web_tracking_key

SERVERSequenzy Mcp SOURCESequenzy/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/io-github-polnikale-sequenzy-mcp/delete-web-tracking-key.md

WHAT IT DOES

What delete_web_tracking_key does on Sequenzy Mcp

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

RISK

Why delete_web_tracking_key is rated Critical

Irreversibly deletes tracking infrastructure; blocks ongoing tracking operations permanently until reinstallation.

From the tool's definition Permanently delete a web tracking key; cached authorization expires; requests rejected.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_web_tracking_key safely

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

delete_web_tracking_key Hidden

delete_web_tracking_key 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_web_tracking_key"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about delete_web_tracking_key

What does the delete_web_tracking_key tool do? +

Permanently delete a web tracking key. Cached authorization expires within one minute, after which requests from any remaining snippet are rejected; remove the snippet from the site as well. Prefer update_web_tracking_key with isActive: false when the key might be needed again. It is categorised as a Destructive tool in the Sequenzy Mcp 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_web_tracking_key? +

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

What risk level is delete_web_tracking_key? +

delete_web_tracking_key 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_web_tracking_key? +

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

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

delete_web_tracking_key is provided by the Sequenzy MCP server (Sequenzy/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sequenzy, and thousands of servers like it.

This server

All 222 Sequenzy tools → Critical-risk tools on this server →

Across the catalogue

delete_ssh_key on cPanel MCP Server →sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →web3_revoke_key on 0xarchive → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →