Templates
A template builds a policy from the abilities registered on your site when the agent is created. Afterwards, the policy is yours to edit. Abilities installed later stay denied until you allow them.
| Template | What the agent can do |
|---|---|
| Read-only auditor | Reads site information and content. Cannot change anything. |
| Content editor (drafts only) | Reads posts and writes drafts. Cannot publish, trash, or delete. |
| Content publisher | Writes and publishes posts. Moving posts to the trash waits for approval. |
| WooCommerce catalog manager | Updates products and stock. Price changes wait for approval. |
| WooCommerce support | Reads orders and adds order notes. Refunds wait for approval. |
| Site maintainer | Reads site information. Plugin and theme updates wait for approval. |
| Full access with approvals | Can request any registered ability. Every change waits for approval. |
Two rules apply to every template:
- A held action can actually be approved. When a template holds an action, it turns off the hard block that would otherwise refuse it.
- The MCP adapter's own meta-tools are never allowed. They would be a second route to every ability.
With policy packs (Pro), the WooCommerce and maintenance templates use exact rules for the plugins a pack knows, instead of matching ability names by word.