site_unprotect

Remove a protection rule set by site_protect. The specified pages/templates become editable again. Use site_protected to see which keys are currently active.

SERVERElementify MCP SOURCEvamerli/elementify-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/vamerli-elementify-mcp/site-unprotect.md

WHAT IT DOES

What site_unprotect does on Elementify MCP

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

RISK

Why site_unprotect is rated Critical

An AI agent that decides to call site_unprotect doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Elementify MCP is gone. There is no undo for destructive operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs site_unprotect safely

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

site_unprotect Hidden

site_unprotect 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": [
    "site_unprotect"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about site_unprotect

What does the site_unprotect tool do? +

Remove a protection rule set by site_protect. The specified pages/templates become editable again. Use site_protected to see which keys are currently active. It is categorised as a Destructive tool in the Elementify 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 site_unprotect? +

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

What risk level is site_unprotect? +

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

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

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

site_unprotect is provided by the Elementify MCP server (vamerli/elementify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Elementify, and thousands of servers like it.

This server

All 269 Elementify tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →