Activity Log abilities, governed through the Bridge

An agent can read a WordPress site's activity log: query and look up individual entries, list the available filter values, summarize activity over a time range, and scan for suspicious events such as failed login bursts.

Abilities
55 read
Active installs
200K+
Rating
86% (74 ratings)
Version checked
2.18.0
Requires
WP 6.2+, PHP 7.4+
Last updated
2026-10-28
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 7.4 or later and the plugin active. The permission check for all 5 abilities runs through a helper or filter, so no single capability is listed here.

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 5 Activity Log abilities

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

Read 5

  • Read

    Query activity logs

    Returns paginated activity log entries with the same filters as the Activity Log admin list.

    Permission
    Custom checkpermission is checked by the plugin's own code, so no single capability could be read from it
    MCP tool
    aafm-bridge-activity-log-query-logs
  • Read

    Get activity log entry

    Returns a single activity log entry by ID.

    Permission
    Custom checkpermission is checked by the plugin's own code, so no single capability could be read from it
    MCP tool
    aafm-bridge-activity-log-get-log
  • Read

    Get activity log filters

    Returns available filter values (users, roles, topics, actions, sources) for the current user.

    Permission
    Custom checkpermission is checked by the plugin's own code, so no single capability could be read from it
    MCP tool
    aafm-bridge-activity-log-get-filters
  • Read

    Summarize activity

    Returns aggregated activity statistics for a time range (counts by action, type, user, channel, and time buckets).

    Permission
    Custom checkpermission is checked by the plugin's own code, so no single capability could be read from it
    MCP tool
    aafm-bridge-activity-log-summarize-activity
  • Read

    Detect suspicious events

    Scans activity log entries for suspicious patterns (failed login bursts, sensitive options, off-hours agent activity).

    Permission
    Custom checkpermission is checked by the plugin's own code, so no single capability could be read from it
    MCP tool
    aafm-bridge-activity-log-detect-suspicious-events

How to switch these on

Four steps from two active plugins to a governed connection.

  1. Install Activity Log and Agent Abilities for MCP

    Both plugins need to be active on the same WordPress site. Activity Log 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 Activity Log 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 Activity Log work with the Bridge?

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

Do Activity Log's abilities register automatically?

Yes, once Activity Log 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 Activity Log 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 7.4 or later and the plugin active. The permission check for all 5 abilities runs through a helper or filter, so no single capability is listed here.

More Developer plugins

An agent can list, read and search custom code snippets and the WPCode library, check snippets for errors, read WPCode's error log and settings, create, update, install and switch snippets on or off, and read or replace the site-wide header, body and footer code.

Developer3M+ active installsVerified 10 November 2026
7 read3 write2 destructive
View abilities

An agent can look up the expected value format for a field type, then read, write, or delete a specific custom field's value on a post, term, user, comment, or settings page.

Developer500K+ active installsVerified 10 November 2026
2 read1 write1 destructive
View abilities

An agent can list, read, create, update, duplicate, export, import, trash, and restore SCF field groups, individual fields, custom post types, taxonomies, and options pages, and, once the site turns on AI Access, list and register field groups, post types, and taxonomies under a second acf/* ability set plus create, read, update, and delete records of any post type or taxonomy the site opts in.

Developer100K+ active installsVerified 28 September 2026
18 read31 write5 destructive
View abilities

Verified from Activity Log's own free wordpress.org code (version 2.18.0) 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, Elementor or Activity Log. Back to the full directory.

Back to the plugin directory

Bridge Activity Log, 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.