Safety controls

On top of the always-on governance model, the plugin offers five optional controls. All five stay off until you set them.

Per-minute rate limit

Set a per-minute cap on the Settings tab under “Rate limit (per minute)”. Each connection can make that many agent calls a minute, counted per agent user, and 0 turns the limit off. Calls over the cap are denied and logged on the Activity Log tab, so you can spot a connection that keeps hitting it.

IP allowlist

Restrict connections to a list of IP addresses you trust. Off until you set it.

Force-to-draft mode

Force new content the agent creates to draft, so nothing an agent writes goes live without a human publishing it.

Title-length cap

Cap the length of titles the agent can set, a small guard against runaway or malformed content.

Block-markup validation

When an agent writes a page, post, template, or reusable block, the plugin steers the styling into block attributes instead of inline CSS and checks the markup before it saves. That keeps agent-authored content from showing up as “invalid content” in the block editor. It warns by default. Turn on strict mode and a block that fails validation is refused rather than saved with a warning.

Layer these on as you need them

None of these are required for the plugin to be safe: least privilege, off by default, capability gating, and the audit log do that work already. These five are extra guards for when you want a tighter box around a specific connection.

Two more switches in the same card

The five above are per-call limits on abilities that are still registered as MCP tools. Two other switches head the same Safety controls card on the Settings tab, and they work a level earlier: they decide what gets registered at all. They sit apart from the five above because they do not share the “off until you set them” promise.

• Read-only mode, off by default, added in 1.6.0. One switch and nothing that writes is registered as an MCP tool, whatever you have ticked, so a blocked write is missing from the agent’s tool list rather than refused when it calls. It covers abilities bridged from your other plugins too, each judged by that plugin’s own annotation, and anything that declares neither way counts as a write and stays out. Turning it on enables nothing by itself, and turning it off enables nothing either.
• The high-risk lock, on by default, added in 1.5.0. The WooCommerce abilities that move money or grant authority stay locked even after you enable them, until you switch the high-risk control on as well. That switch is written to the audit log.

Both are covered in full on Features and Security.

Next steps

• Governance concepts: the always-on model underneath.
• Security: read-only mode and the high-risk lock in full, plus what each credential reaches.
• Troubleshooting: common connection snags and fixes.