Skip to main content
By default the server exposes its full tool catalog. Two settings narrow it:
  • allowedTools: a whitelist. Only the listed tools exist as far as the AI is concerned.
  • blockedTools: a blacklist. Everything is available except the listed tools.
When both are set, the whitelist applies first, then the blocklist filters the result. Tool names use underscores (list_sites_v1, not list-sites-v1). Filtering removes a blocked tool everywhere it could be seen or used: tool listing, execution, completions, per-tool help, and the informational resources. The AI cannot call what it cannot see.

Ready-made configurations

Read-only monitoring (17 tools). For dashboards, reporting, and any setup where the AI should observe but never modify. This is the configuration to reach for when safe mode is not strict enough, since safe mode still allows updates and activations.
Updates only (13 tools). Focused update management for maintenance automation and CI pipelines.
Site management only (30 tools). Full site management without client, tag, or update management.
Hide destructive tools. Keep all functionality while removing deletions from the AI’s view. A conservative default for production.
Minimal update automation (4 tools). Just enough to check and apply updates; pairs well with compact schemas for the smallest possible context footprint.

Tools from other namespaces

If you have exposed abilities from other plugins, their tools carry a namespace prefix, and the filter lists must use the prefixed form:

Notes

  • Two built-in resources, mainwp://categories and mainwp://status, stay unfiltered by design: they describe the Dashboard connection, not the tool surface. See Tools & Resources.
  • Filtering also reduces the token cost of the tool catalog in the AI’s context window; the Optimize Token Usage guide has the numbers.