I've spent enough time in production environments to know that 'access control' is usually where automation goes to die.
You want the magic of an AI agent—you want Claude to act as a concierge, handling signups or managing memberships—but the moment you give an LLM access to your WordPress REST API with broad permissions, you've essentially handed a loaded gun to someone who might hallucinate under pressure.
The fear isn't just that the AI will make a mistake. The fear is that a prompt injection or a simple logic error results in role: admin instead of role: subscriber. If you're an engineer, you know that relying on the LLM to "follow instructions" for security is not a strategy. It's a vulnerability.
That’s exactly why we built the WordPress Subscriber Creator. We didn't build it by trying to make a 'better' WordPress integration. We built it by intentionally breaking as many features as possible.
The Fallacy of Permission via Prompting
