Capabilities and scopes

Every tool belongs to a capability. A capability that is off is refused server-side: the tool is not even listed to the assistant.

​

Site capabilities

Set under Bevel → MCP Connectors → Capabilities. They apply to every connection. get_build_guide needs no capability: reading the rules is always allowed. All capabilities are on by default. The whole plugin is opt-in, so the switches are for narrowing.

​

Per-connection scopes

Each connection can be narrowed further. Open Scopes on the connection row, untick what this connection may not do, and save. A connection’s scopes are always a subset of the site’s capabilities: the site switch wins. Use it to give a client’s own assistant read-only access, to let a copywriting session touch posts but not the header, or to keep a testing connection away from maintenance tools.

​

What edits need

The capability follows the document, not the tool. update_page on a template needs Theme Builder templates; on a post it needs Blog posts; on a page it needs Page creation. A connection with only Page creation cannot rewrite the live header.

​

What no capability allows

There is no tool that deletes a page, a post, a template or a menu. The catalogue creates and updates, and an update replaces the content of something you can already see. Pages are created as drafts unless the assistant is asked to publish. The one tool that removes anything is the database cleanup, and only on an explicit second call after it has reported what it would remove.