Troubleshooting

Access denied

Identify the access layer refusing an action and change only the permission you intend to grant.

An access refusal is different from a WordPress execution failure. Repeating an unchanged request does not grant permission. Keep the error code and check the layer it names.

Match the refusal to its setting

MCP_SITE_EXECUTION_DENIED: this connection is not allowed to access the selected website. Review its website access in Agents.
AGENT_ABILITY_MODE_DENIED: the Ability is outside the Agent's mode. Choose an allowed action or deliberately review its mode.
TOOL_PACK_NOT_GRANTED: the Toolkit is outside this connection's allowed groups. Review the Agent's Manage access selection.
TOOL_PACK_DISABLED: the Toolkit is not enabled for the Workspace. Review its configuration under Abilities.
ABILITY_DISABLED: the individual Ability is not enabled for the Workspace. Review Manage for its Toolkit.
SITE_TOOL_DISABLED: the Ability is disabled for this website. Review the website's Ability settings.
DANGEROUS_TOOLS_DISABLED: MoraWP's platform safety control blocks high-impact work. A Workspace switch cannot override it.

If you cannot manage the relevant setting, ask the person who owns that connection or the Workspace to review it. Do not send them credentials.

Understand the Agent's mode

Read only: reads within the Workspace and website rules.
Recommended: reads and ordinary edits within those rules, excluding high-impact work.
Everything allowed: every action the Workspace and website permit, including high-impact Abilities they explicitly enabled.
Chosen groups: selected Ability groups within those same restrictions. This option appears in connection management, not the initial approval picker.

These are the Agent connection labels. Workspace and website configuration can use Full access, Custom, or Its own settings for their own controls. An Agent's broader mode cannot enable an Ability that those layers block.

Read only limits changes, not data sensitivity. Enabled Integration reads can return private settings and credentials. Review data access before approving an app, even if you only intend to read.

For high-impact actions

The Workspace must explicitly enable the individual high-impact Ability. Enabling a Toolkit or choosing an Agent's broader mode alone does not do that. Recommended continues to exclude high-impact actions.

Confirm the intended website, action, and access before changing a setting. Then ask the Agent to discover the currently available Ability and schema. High-impact actions use the same AI Actions allowance as other Abilities.

If this is not an access refusal

MCP_ABILITY_NOT_FOUND calls for fresh discovery. MCP_DRY_RUN_UNSUPPORTED means the requested dry run is unsupported, not that it is safe to remove the dry-run flag automatically.

If an action was dispatched and failed, check WordPress tool failed and inspect the website before repeating a change. An error does not prove that nothing changed.

Missing Abilities

Check the website, installed Integration, and access settings when an action is unavailable.