---
title: "Tools available over MCP"
description: "Which MazeGraph tools an MCP app can call, how the list follows the Tools catalogue, and what stays unavailable."
image: "https://mazegraph.com/docs/og.png"
---

> Documentation Index
> Fetch the complete documentation index at: https://mazegraph.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Tools available over MCP

MazeGraph does not keep a separate permanent allowlist of MCP tools. The MCP server takes its available tools from the same MazeGraph catalogue as chat. A built-in ability is eligible when it is MazeGraph-owned, has a read effect, includes the MCP surface, is registered by an active module, and is switched on. MazeGraph then checks the current administrator's WordPress permissions and policy for the request.

The exact list can differ by WordPress version, active plugins, WooCommerce availability, module state, tool switches and the person's permissions. The [full tool reference](/docs/tools/) lists each static ability and its possible surfaces. The catalogue and MCP settings show the live availability on this site.

## What is never offered

- MazeGraph write tools are not offered over MCP. Outside apps cannot submit an approval or claim a person-originated action.
- Third-party publisher abilities and WordPress Core abilities are not served by MazeGraph's own MCP server.
- A tool without the MCP surface, a disabled tool, or a tool whose permission check fails is unavailable.

A direct WordPress MCP Adapter default server has a separate **Share read-only tools with MCP apps** setting. It can expose eligible read-effect MazeGraph abilities through the WordPress Abilities API; the registered permission callback and MazeGraph's DirectCallGuard still run. That direct path does not create the normal Bridge tool-execution Activity record. See [MCP security and access](/docs/mcp/security-and-access/) for the difference between the two host paths.

## Default and sensitive reads

The recommended set on sites with no previous MazeGraph sessions and after **Reset to recommended** contains eight reading tools:

- <code>maze-graph/search-content</code>
- <code>maze-graph/get-content</code>
- <code>maze-graph/list-content</code>
- <code>maze-graph/content-summary</code>
- <code>maze-graph/list-post-types</code>
- <code>maze-graph/list-terms</code>
- <code>maze-graph/list-media</code>
- <code>core/get-site-info</code>

No write tools are in that set. Sites with prior sessions keep their earlier defaults unless an administrator resets them. During the 1.3.0 upgrade, if MazeGraph's MCP server or the MCP Adapter sharing switch was enabled, any enabled tool from the fourteen-tool former held-back list is switched off once. The migration records this change and does not re-enable them later. Other existing settings are preserved.

Personal and WooCommerce reads are not permanently blocked from MCP. An administrator can enable an eligible read tool in the Tools catalogue. Such tools still check the WordPress permission for the current person and may return personal or financial data to the connected app. Enable only the data access the app needs.

## Tool names and results

MCP names use an underscore after the namespace, so <code>maze-graph/list-plugins</code> appears as <code>maze-graph_list-plugins</code>. Results are bounded and treated as untrusted site data. The MCP client should treat result text as data, not instructions, and should follow its own privacy and retention controls.

Source: https://mazegraph.com/docs/mcp/tools-available-over-mcp/index.mdx
