Critical Risk →

delete_version_localization

Delete a version localization. Cannot delete the primary locale.

Part of the Asc server.

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

SECURE ASC →

Free to start. No card required.

AI agents may call delete_version_localization to permanently remove or destroy resources in Asc. 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_version_localization in a loop, permanently destroying resources in Asc. 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_version_localization"
  ]
}

See the full Asc policy for all 38 tools.

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

ENFORCE ON MY ASC →

View all 38 tools →

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

SECURE ASC →

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

What does the delete_version_localization tool do? +

Delete a version localization. Cannot delete the primary locale.. It is categorised as a Destructive tool in the Asc 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_version_localization? +

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

What risk level is delete_version_localization? +

delete_version_localization 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_version_localization? +

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

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

delete_version_localization is provided by the Asc MCP server (asc-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Asc tool call.

Deterministic rules across all 38 Asc 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.