woo_helper_create_invoice
DESTRUCTIVE, IRREVERSIBLE: creates a REAL invoice for this order in the live sevDesk/Lexware ledger. An invoice there cannot be deleted, only cancelled with a cancellation invoice. Refused with 409 while dry-run is on. Check woo_helper_get_invoice_order (preview) first. Requires confirm:true.
This record as markdown: /tools/io-github-cvrt-jh-wordpress-mcp/woo-helper-create-invoice.md
What woo_helper_create_invoice does on Wordpress
AI agents call woo_helper_create_invoice 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.
Why woo_helper_create_invoice is rated Critical
Creates permanent financial records in external ledger that cannot be undone, only cancelled.
From the tool's definition DESTRUCTIVE, IRREVERSIBLE: creates REAL invoice in live sevDesk/Lexware ledger. Cannot be deleted.
Attacks that exploit this kind of access
The rule that runs woo_helper_create_invoice 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 woo_helper_create_invoice, this is the rule to start with:
woo_helper_create_invoice 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 Wordpress, apply this rule, and every woo_helper_create_invoice call is checked against it from then on.
Questions about woo_helper_create_invoice
DESTRUCTIVE, IRREVERSIBLE: creates a REAL invoice for this order in the live sevDesk/Lexware ledger. An invoice there cannot be deleted, only cancelled with a cancellation invoice. Refused with 409 while dry-run is on. Check woo_helper_get_invoice_order (preview) first. Requires confirm:true. 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.
Register the Wordpress MCP server in PolicyLayer and add a rule for woo_helper_create_invoice: 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.
woo_helper_create_invoice 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 woo_helper_create_invoice 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 woo_helper_create_invoice. 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.
woo_helper_create_invoice 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.
More on Wordpress, and thousands of servers like it.
Across the catalogue