Skip to content

A tool is missing or refused

Updated View as Markdown

A tool can be missing from the chat, appear unavailable in the catalogue, or appear in chat and then be refused. Those symptoms point to different checks. MazeGraph does not use a shared administrator account: a chat tool call runs with the WordPress permissions of the person who sent the message.

Start by noting which assistant you selected, which tool you expected, and what message or status you saw. Then ask a site administrator to follow the checks below. For the underlying access model, see Who may use tools and How MazeGraph decides what may happen.

If a tool is missing from chat

The catalogue and the assistant’s tool list are separate. A tool may exist on the site but not be enabled, not be included for the selected assistant, or not be available from the plugin or extension that provides it.

Check What to do
Site-wide tool availability Open MazeGraph → Settings → General → Availability and make sure Allow tool use is on. This is separate from Allow new replies. See General settings.
Tool and extension Open MazeGraph → Tools → Tools. Find the tool, review its status or availability reason if shown, and check that its tool switch and the extension that provides it are enabled. Tools supplied by another plugin also depend on that plugin being installed and active. See the tool catalogue and Extensions.
Selected assistant Open MazeGraph → Tools → Agents and check that the selected assistant includes the tool. The built-in main assistant can be given access to all enabled tools in Settings → Tools; other agents retain their own tool lists.
Workspace access If MazeGraph itself is unavailable, ask an administrator to check who may open the workspace. Workspace access does not, by itself, grant access to tools. See Availability and role access.

If the tool is absent from the catalogue too, check whether the required WordPress plugin, MazeGraph extension, or supported integration is active. The catalogue changes with the tools provided by the current WordPress installation. A tool can be listed but still unavailable to a particular person or assistant.

If a tool appears but will not run

Use the refusal or availability message to identify the failed check. Then review these controls with an administrator:

  1. Confirm the tool is enabled. In MazeGraph → Tools → Tools, check the tool’s own switch and its availability status. A group-level action can change multiple tools, so verify the specific tool as well.
  2. Confirm the assistant includes it. The selected agent must be allowed to use the tool. The main-assistant setting does not change another agent’s list.
  3. Check the current person’s WordPress permission. MazeGraph checks the capability needed for the specific action and, where relevant, the target post or other content. Changing the assistant list cannot grant that WordPress permission.
  4. Check site policy and safeguards. Consent, usage limits, a site or extension rule, or a write-safety check can stop an otherwise enabled tool. Usage limits and Policy Administration and Safeguards explain these controls.
  5. Distinguish a refusal from an approval request. A write that is waiting for your review has not necessarily been refused. Read the proposed change and decide whether to approve it. Approval modes cannot override a missing capability or a policy denial; see Approval modes.

The Ask, Auto, and Full modes only change when supported writes ask for approval. They do not switch tools on, expand an agent’s tool list, or grant WordPress capabilities.

Examples

An editor can chat but cannot count users

An editor can open the workspace and send a message, but the Count users tool is refused. That tool requires the WordPress list_users capability. An administrator can confirm the tool and assistant settings, but enabling either one will not add that capability to the editor’s account. The site administrator must decide whether the person should receive the required WordPress permission.

Likewise, Get site settings requires manage_options, and List plugins requires activate_plugins. These checks protect sensitive site information and administrative actions. See Who may use tools for more examples.

A draft change is waiting for approval

If an assistant proposes a draft change and an approval card appears, this is a review step rather than a missing-tool error. Check that the proposed content and target are correct, then approve or refuse it. If the tool is refused before an approval card appears, check the tool switch, assistant scope, WordPress capability, and policy rules. Review changes and undo describes what happens after a supported write.

A tool is unavailable only for some requests

Some policy checks depend on the current request or session. For example, a limit can prevent more work after the site’s allowance is reached, and tools may not be offered during the model’s final response step. Check the refusal details and the site’s usage controls; do not treat an intermittent or request-specific refusal as proof that the tool has been removed. See Usage and activity and Usage limits.

A quick administrator checklist

When investigating a report, check the same person, assistant, and task that produced it:

  1. Can the person open the workspace?
  2. Is Allow tool use on in MazeGraph → Settings → General → Availability?
  3. Is the tool enabled, and is its providing extension or plugin active?
  4. Does the selected assistant include the tool?
  5. Does the current WordPress user have permission for this exact action and target?
  6. Is a consent, usage limit, policy rule, or write approval involved?

If the action was recorded, review the relevant entry in Activity and usage. Share the refusal text and the tool name when asking for help, but do not include provider credentials, private content, or personal data.

Example: access denied for a user-count request

What happened: A person could chat with MazeGraph, but a request to count WordPress users was refused. Reason: The tool requires the list_users capability, which that person’s WordPress account did not have. Solution: The administrator verified the tool switch and assistant list, then reviewed whether the person’s role should be granted the needed capability. Learning: When a tool is refused, check the current user’s permission for the exact task; workspace access and assistant access do not replace WordPress capabilities.

For related access questions, continue with Availability and role access, Who may use tools, and Approval modes.

Was this page helpful?

Your feedback helps us improve these docs.

Documentation

Type to search…

↑↓ navigate↵ selectEsc close