site_protect
Protect specific pages or templates from being modified by any agent tool. Sets an enforced rule in site memory — the plugin will refuse writes (HTTP 423) to protected content. The protection is NOT a warning; it is an actual refusal. Use site_unprotect to remove protection, or site_protected to ...
This record as markdown: /tools/vamerli-elementify-mcp/site-protect.md
What site_protect does on Elementify MCP
AI agents call site_protect 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.
Why site_protect is rated Critical
An AI agent that decides to call site_protect 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
The rule that runs site_protect 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_protect, this is the rule to start with:
site_protect is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Elementify MCP, apply this rule, and every site_protect call is checked against it from then on.
Questions about site_protect
Protect specific pages or templates from being modified by any agent tool. Sets an enforced rule in site memory — the plugin will refuse writes (HTTP 423) to protected content. The protection is NOT a warning; it is an actual refusal. Use site_unprotect to remove protection, or site_protected to list current rules. 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.
Register the Elementify MCP server in PolicyLayer and add a rule for site_protect: 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.
site_protect is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the site_protect 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.
Set action: deny in the PolicyLayer policy for site_protect. 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.
site_protect 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.
More on Elementify, and thousands of servers like it.
Across the catalogue