> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wpbevel.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Capabilities and scopes

> What a connected assistant is allowed to do, per site and per connection.

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.

| Capability                   | Tools it unlocks                                                                                  |
| ---------------------------- | ------------------------------------------------------------------------------------------------- |
| Read site content            | `list_pages`, `get_page`, `list_menus`                                                            |
| Design System updates        | `get_design_system`, `update_design_system`, `revert_design_system`, `upload_font`                |
| Page creation                | `create_page`, `update_page`, `build_page`                                                        |
| Theme Builder templates      | `create_template`                                                                                 |
| Blog posts                   | `create_post`                                                                                     |
| Site settings                | `update_site_settings`, `update_site_logo`, `generate_logo`                                       |
| Menus                        | `add_to_menu`                                                                                     |
| Media library                | `upload_media`, `list_media`, `set_image_alt`, `search_images`, `get_brand_assets`, `fetch_brand` |
| Meta descriptions            | `set_meta_description`                                                                            |
| Site maintenance             | `optimize_site`, `convert_webp`, `clear_cache`, `optimize_database`                               |
| Form submissions (read-only) | `list_form_submissions`                                                                           |

`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.