Agent Abilities
GitHubGet it free
Product
FeaturesSecurityAll abilitiesIntegrationsBridge overviewBridge plugin directory196

Guides

WordPress MCP serverAbilities API guideElementor MCP

WordPress core abilities

Browse all abilitiesContentTaxonomies & TermsCommentsUsersMediaSite settingsPluginsThemes & stylesBlocksMenusSearch

Integrations

All integrationsWooCommerce52Advanced Custom Fields7Rank Math SEO5Yoast SEO3All in One SEO3Slim SEO2The Events Calendar13Event Tickets3Avada2GeoDirectory4

Bridge, most installed

Elementor Website BuilderYoast SEOWooCommerceAkismet Anti-spamWPFormsRank Math SEOWP Mail SMTPWPCode
Connect
All clientsChatGPTClaude.aiClaude DesktopManusClaude CodeCursorVS CodeWindsurfGemini CLIGetting startedHow connecting works
Resources
Prompt LibraryPlaybooksBlogComparisonsChangelogSupport
DocsGitHubGet it free

Governed ability

Get playbook

aafm/get-playbookRead only

Get playbook is a governed ability in Agent Abilities for MCP, a free WordPress plugin that runs an MCP server on your site.

Load one of the site owner's playbooks by slug: the steps to follow, the abilities it uses and which of those you cannot use on this connection. The steps name tools by label; the abilities list gives the tool to call for each.

How it is governed

The same model as every ability in the plugin, stated for this one.

  • Off until you enable it

    Like every ability, Get playbook ships switched off. You turn it on one at a time, and an update never switches on a tool it serves.

  • Reads only

    It reads data and returns it to your client. Nothing on your site is created, changed, or removed.

  • Capability gated

    A connection only sees Get playbook if the user you connected can run it, and the plugin checks that capability again before it executes.

  • Every call audited

    The call is written to the log in your own database, denials included, with the argument keys and the identifiers it touched, never free-text content.

Get playbook is one of the 8 governed Site settings abilities. Browse the other Site settings abilities in the catalog.

See it in action

An illustrative run. Your real calls and data stay on your own site.

agent-abilities · auditGoverned
YouGet playbook on this site.
RunRunning aafm/get-playbook
GateAllowedread capability confirmed
Auditaafm/get-playbook · principal: editor · args: keys
ResultReturns the data the agent asked for. Nothing on the site changes.

Try it with a prompt

Example requests you could paste to your agent.

  1. Load the publish checklist playbook and follow it for my latest draft.
  2. Open the weekly content report playbook and run it.
  3. Read the shop tidy-up playbook and tell me which of its tools you can use here.

These are illustrative example prompts. The agent runs them as the user you connected, checked against that user's capabilities and written to your audit log.

Frequently asked

Short answers for Get playbook.

What does it return?

Get playbook loads one Active playbook by slug: the steps the site owner wrote, the abilities it uses, and which of those this connection cannot use, so the agent can say up front what it will not be able to do.

Does loading a playbook switch on the tools it names?

No. A playbook is instructions, not permissions. The agent can only call the abilities you enabled, as the WordPress user it connected as, and every call is still checked and logged.

Related abilities

More in Site settings.

Get activity log

Read only

Reads this plugin's own audit log: each row's ability name, status (started, success, error, denied), acting user id and login, whether the caller is flagged as an agent identity, the argument keys passed, the timestamp, and a short identifier-only detail (an object id or slug, a WP_Error code, or a crashed call's exception class and throw site; a code returned by another plugin's bridged ability is prefixed with foreign:). Most recent first. Response includes total (the count for the status filter). Never free-text argument content or network addresses. Requires the manage-options capability.

View ability

Get site settings

Read only

Read a small allowlist of site settings: name, tagline, timezone, date and time formats, week start, and posts per page. Requires the manage-options capability. Never the site URL or admin email.

View ability

Update site settings

Guarded write

Write a small allowlist of site settings, passed as a settings object whose keys are the setting names and values the new values. Accepted keys: blogname (site name), blogdescription (tagline), timezone_string, date_format, time_format, start_of_week (0-6), posts_per_page (1-100). String values are sanitized; the two integer settings are clamped into their legal ranges. Any unrecognized key rejects the entire call with nothing written. It can never change the site URL, admin email, default role, or open registration. Requires manage-options. Off by default.

View ability

Get taxonomies

Read only

List public taxonomies registered on the site.

View ability

Get post types

Read only

List public post types registered on the site. Each type includes two flags: writable (agents may create items of that type) and updatable (agents may also update or delete existing items; false for types that opt out of WordPress capability mapping, which are create-only through these abilities).

View ability

Get site info

Read only

Retrieve the site name, tagline, URL, and language.

View ability

Back to all abilities

Governed by default, from the first call.

Get playbook is off until you enable it, scoped to the user you connect, and logged like everything else. Turn on only what you need.

Get it on WordPress.orgRead the docs

Every ability off until you enable it, capability-gated on every call.