Lazy Blocks abilities, governed through the Bridge

An agent can list Lazy Blocks blocks with their ID, title, status and slug, read one block's full builder data (controls, code, supports, styles, condition), create and publish new blocks, and update the title or builder data of existing ones.

Abilities
42 read1 write1 destructive
Active installs
20K+
Rating
98% (80 ratings)
Version checked
4.5.1
Requires
WP 6.2+, PHP 8.3+
Last updated
2026-10-26
Abilities verified
10 November 2026
Installs and rating as of
10 November 2026

What has to be true first

The Abilities API itself needs WordPress 6.9 or later (the plugin lists WordPress 6.2), plus PHP 8.3 or later and the plugin active. The abilities check these capabilities: edit_lazyblocks, edit_post.

A note on the count below

Counted from the plugin code on 10 November 2026; settings or feature flags that the count does not evaluate may hide some of these abilities.

The 4 Lazy Blocks abilities

Grouped by what each one can change. Every one starts off until you enable it.

Destructive also covers abilities the plugin does not declare read-only: the Bridge treats a missing annotation as destructive until the owner reviews it, so some of them may only look things up.

Read 2

  • Read

    List Lazy Blocks

    Returns the blocks made in the Lazy Blocks builder with their ID, title, status and slug.

    Permission
    edit_lazyblocks
    MCP tool
    aafm-bridge-lazy-blocks-list-blocks
  • Read

    Get Lazy Block

    Returns one Lazy Blocks block with all its builder data: controls, code, supports, styles and condition.

    Permission
    edit_lazyblocks
    MCP tool
    aafm-bridge-lazy-blocks-get-block

Write 1

  • Write

    Create Lazy Block

    Creates and publishes a new Lazy Blocks block. Data keys not given take the builder defaults.

    Permission
    edit_lazyblocks
    MCP tool
    aafm-bridge-lazy-blocks-create-block

Destructive 1

  • Destructive

    Update Lazy Block

    Updates the title or builder data of a Lazy Blocks block. Only the given top-level data keys change, and each given key is replaced whole: a given controls or supports object replaces the stored one instead of merging into it.

    Permission
    edit_postWhoever can edit that post
    MCP tool
    aafm-bridge-lazy-blocks-update-block

How to switch these on

Four steps from two active plugins to a governed connection.

  1. Install Lazy Blocks and Agent Abilities for MCP

    Both plugins need to be active on the same WordPress site. Lazy Blocks registers its own abilities; this plugin discovers and governs them.

  2. Open the Plugins’ own tools screen

    In Agent Abilities for MCP, open the Bridge tab (labeled "Plugins’ own tools" in the admin, "Other plugins" before 1.12.0). Abilities from every registered plugin appear there, grouped by the plugin that registered them.

  3. Enable one ability at a time

    Every ability from Lazy Blocks starts off. Turn on only the ones you want an agent to reach, or enable the whole set in one click.

  4. Connect as a least-privilege user

    Approve the connection as a WordPress account scoped to what you actually want the agent to do. Each call still re-checks that account’s capability before it runs.

Read more in how bridging works or the full documentation.

Frequently asked questions

Does Lazy Blocks work with the Bridge?

Yes. Lazy Blocks calls wp_register_ability() for 4 abilities in its current code on wordpress.org, so the Bridge can discover them once the plugin is active.

Do Lazy Blocks's abilities register automatically?

Yes, once Lazy Blocks is active, as far as its code shows. This directory reads the code but does not evaluate every setting or feature flag, so check the plugin's own settings if an ability is missing on your site.

Does Lazy Blocks need anything special to work with the Bridge?

The Abilities API itself needs WordPress 6.9 or later (the plugin lists WordPress 6.2), plus PHP 8.3 or later and the plugin active. The abilities check these capabilities: edit_lazyblocks, edit_post.

More Page builders plugins

An agent can read and edit the structure of Elementor-built pages, list and inspect widget and component schemas, manage the site's shared global CSS classes and design-token variables, build whole page layouts from a composition description, and publish or preview documents.

Page builders10M+ active installsVerified 28 September 2026
9 read5 write13 destructive
View abilities

Once enabled, an agent can read and manage HFE header/footer/block templates and Elementor pages end to end: list, create, update, duplicate, delete and restore templates and pages, build and edit Elementor layouts widget by widget, toggle widgets and extensions, set display rules and theme compatibility, read the site's design tokens, and clear the Elementor CSS cache.

Page builders2M+ active installsVerified 28 September 2026
17 read22 write6 destructive
View abilities

An agent can list and insert ElementsKit's widgets and templates into Elementor pages, scaffold new pages, headers, footers and custom widgets, and manage mega menus, all with an unauthenticated caller in mind since the code carries no readonly or destructive annotations.

Page builders1M+ active installsVerified 10 November 2026
15 destructive
View abilities

Verified from Lazy Blocks's own free wordpress.org code (version 4.5.1) on 10 November 2026, not from its marketing claims. Not every ability listed here has been run end to end against a live site. Plugin authors change their code, so a name, a capability, or a condition can be different in a later release. This site is not affiliated with, or endorsed by, nK or Lazy Blocks. Back to the full directory.

Back to the plugin directory

Bridge Lazy Blocks, keep the same control.

Every ability starts off, is scoped to the user you connect, and is written to the same audit log as core. Turn on only what you need.

Off by default. Capability checked on every call.