stripe_recreate_webhook

Recreate this site

SERVERWordpress SOURCE@cavort-it-systems/wordpress-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/io-github-cvrt-jh-wordpress-mcp/stripe-recreate-webhook.md

WHAT IT DOES

What stripe_recreate_webhook does on Wordpress

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

RISK

Why stripe_recreate_webhook is rated Critical

Recreating a site implies destructive replacement of existing site data and configuration.

From the tool's definition Recreate this site

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs stripe_recreate_webhook safely

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

stripe_recreate_webhook Hidden

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

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about stripe_recreate_webhook

What does the stripe_recreate_webhook tool do? +

Recreate this site. It is categorised as a Destructive tool in the Wordpress 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 stripe_recreate_webhook? +

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

What risk level is stripe_recreate_webhook? +

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

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

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

stripe_recreate_webhook is provided by the Wordpress MCP server (@cavort-it-systems/wordpress-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Wordpress, and thousands of servers like it.

This server

All 314 Wordpress tools → Critical-risk tools on this server →

Across the catalogue

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

Guides

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