An agent can check whether a specific comment looks like spam and pull the site's antispam performance statistics.
SAML Single Sign On - SSO Login abilities, governed through the Bridge
An agent can inspect and adjust the plugin's SAML single sign-on configuration: show the current SSO setup, look up identity provider names and setup guides, enable or disable the SSO login button, apply two named certificate/entity-ID fixes, change the default role assigned to SSO users, fetch the service provider metadata URL, and submit a support request.
- Abilities
- 1010 read
- Active installs
- 10K+
- Rating
- 98% (397 ratings)
- Version
- 6.0.0
- Requires
- WP 3.7+, PHP 5.6+
- Last updated
- 2026-09-17
View SAML Single Sign On - SSO Login on WordPress.org
What has to be true first
Needs WordPress 6.9 or later with SAML Single Sign On - SSO Login active and its Abilities API setting turned on. Every one of its 10 abilities checks the manage_options capability, so only a WordPress administrator can use them through the Bridge.
- The plugin's own Abilities API setting (`mo_saml_enable_abilities_api`) must be turned on by an administrator in the plugin's settings; it is off by default.
- Turning that setting on itself requires WordPress 6.8 or later and an installed MCP adapter class (`WP\MCP\Core\McpAdapter`); the plugin forces the setting back off and shows an error if either is missing.
A note on the count below
10 abilities read directly from the plugin's full registration file (class-mo-saml-register-abilities.php), matching the directory's count of 10 exactly. Every one of them sets the annotation `readonly => true` in the source even though several (fix-wpsamlerr010, fix-wpsamlerr012, update-default-role, enable-sso-button, disable-sso-button) call update_option() and change state; the Bridge reads the annotation as stated, so all 10 land in the read risk tier despite five of them writing to the database.
The 10 SAML Single Sign On - SSO Login abilities
Grouped by what each one can change. Every one starts off until you enable it.
Read 10
- Read
Get IDP Name
Fetches the name of the connected identity provider.
- Read
Fix Entity ID WPSAMLERR010
Overwrites the configured entity ID with the value the IDP requires.
- Read
Fix Iconv Certificate WPSAMLERR012
Disables certificate encoding to work around an iconv-related certificate error.
- Read
Update Default Role
Changes the WordPress role assigned to new users who sign in through SSO.
- Read
Show SSO Configurations
Reports the plugin's current SAML SSO configuration across all tabs.
- Read
Get IDP Guide Links
Returns setup guide links for one or more named identity providers.
- Read
Enable SSO Button
Turns on the SSO login button on the WordPress login page.
- Read
Disable SSO Button
Turns off the SSO login button on the WordPress login page.
- Read
Send Support Request
Submits a support question to miniOrange on the site owner's behalf.
- Read
Get SP Metadata
Returns the site's SAML service provider metadata URL.
No abilities match that search.
How to switch these on
Four steps from two active plugins to a governed connection.
Install SAML Single Sign On - SSO Login and Agent Abilities for MCP
Both plugins need to be active on the same WordPress site. SAML Single Sign On - SSO Login registers its own abilities; this plugin discovers and governs them.
Open the Other plugins screen
In Agent Abilities for MCP, open the Bridge tab (labeled "Other plugins" in the admin). Abilities from every registered plugin appear there, grouped by the plugin that registered them.
Enable one ability at a time
Every ability from SAML Single Sign On - SSO Login starts off. Turn on only the ones you want an agent to reach, or enable the whole set in one click.
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 SAML Single Sign On - SSO Login work with the Bridge?
Conditionally. The plugin only registers its 10 SAML configuration abilities when an administrator turns on its own Abilities API toggle in the plugin's settings (off by default); once that is on, the abilities sit in the core registry and the Bridge can wrap them.
What has to be true for SAML Single Sign On - SSO Login's abilities to register?
The plugin's own Abilities API setting (`mo_saml_enable_abilities_api`) must be turned on by an administrator in the plugin's settings; it is off by default.. Turning that setting on itself requires WordPress 6.8 or later and an installed MCP adapter class (`WP\MCP\Core\McpAdapter`); the plugin forces the setting back off and shows an error if either is missing..
Does SAML Single Sign On - SSO Login need anything special to work with the Bridge?
Needs WordPress 6.9 or later with SAML Single Sign On - SSO Login active and its Abilities API setting turned on. Every one of its 10 abilities checks the manage_options capability, so only a WordPress administrator can use them through the Bridge.
More Security & privacy plugins
An agent can check exactly where comments are currently disabled across the site or a multisite network, turn comments off or on for specific post types, and delete existing comments.
An agent can search and read the WordPress activity log: recent events, a single event's detail, one user's activity, failed login attempts, and a statistics summary grouped by users, content, media, plugins, core and notes, all without being able to change anything.
Verified from SAML Single Sign On - SSO Login's own free wordpress.org code on 28 September 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, miniOrange or SAML Single Sign On - SSO Login. Back to the full directory.
Bridge SAML Single Sign On - SSO Login, 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.