Official MCP: per-tool permissions and multi-site management for agency use

Describe the Problem We're an IT services company (NewmountainsIT, Germany) running Elementor sites for SMB clients. We already drive Elementor from Claude Code daily through a community MCP implementation, and the official MCP announced for September is something we want to standardise on. The blocker for production use is access granularity. An MCP client gets an agent that can create pages, change page and site settings, and publish — against a live client site. Prompt injection and tool-poisoning are documented risks in MCP setups, and one bad tool call on a client's production site is a business problem, not a technical one. If the official MCP ships as a single all-or-nothing connection, we can only use it on staging. That removes most of its value: the sites where an agent saves us real time are the ones under maintenance contracts. A second blocker is planning. Angie is free with a daily credit limit. Whether that limit also applies to MCP tool calls decide…