A saved cron tool list still names every enabled MCP server

John Burns

The cron platform list named two toolsets, web and file, plus the sentinel no_mcp. After one disable command that did not turn any new toolset off, the sentinel was gone and the file named only file and web. A paused job created by the CLI stored enabled_toolsets as null. The function the scheduler passes into the agent constructor then returned four names: file, gauge, web, and word_nope.

hermes tools list --platform cron still marked only web and file enabled. hermes cron list printed the job name, the schedule, paused, and the delivery target. hermes cron doctor printed that it found no issues. None of those commands printed gauge or word_nope.

That split is what Hermes Agent 0.22.5 did on 16 November 2026. hermes --version reported v0.22.5+471.g5894e75, commit 5894e750c3db, on Linux x86_64. The CLI actions ran through that wrapper, which reported Python 3.14.9. The constructor list was produced by calling _resolve_cron_enabled_toolsets from the same checkout, under the checkout virtualenv’s Python 3.11.15, because that environment is the one that can import the cron package. The job was not fired. No MCP server process was started. No model call was made. The home was a new directory passed as HERMES_HOME, not the operator home.

The cron page, fetched the same night, says the cron agent gets the toolset configured for the cron platform in hermes tools, not the CLI default. It says a per-job enabled_toolsets list wins when it is set, and otherwise the cron-platform config wins. Its example is ["web", "file"], with the comment that this is just web and file, not terminal or browser. The page also says a cron-platform block that cannot be read fails the run, and it points at hermes cron list and hermes cron doctor for that failure. It does not mention MCP server names being added to a list that looks narrow, and it does not mention a sentinel that keeps them off.

Which server blocks count as enabled

Four server blocks were written under mcp_servers. Each command was /bin/false, so a later start would exit immediately. This run never started them. The resolver only needed the name and the enabled flag.

mcp_servers:
  gauge:
    command: /bin/false
    args: ["gauge"]
  quiet:
    command: /bin/false
    args: ["quiet"]
    enabled: false
  word_off:
    command: /bin/false
    args: ["word-off"]
    enabled: "off"
  word_nope:
    command: /bin/false
    args: ["word-nope"]
    enabled: "nope"

gauge has no enabled key. It was treated as on. quiet has boolean false and stayed off. word_off has the string off and stayed off. word_nope has the string nope. Reading that flag printed:

MCP config expected a boolean-ish value, got 'nope'; using default=True

The warning names the default. The default is on. word_nope was then in the enabled set beside gauge. An unparseable flag is not a disable. The words that did disable, in this run, were boolean false and the string off. The string nope did not.

The set the resolver called enabled was therefore gauge and word_nope. quiet and word_off were in the file and in the list output, and they were absent from every resolved allowlist below.

The list command is not the run list

Before any disable, the cron platform list in the file was:

platform_toolsets:
  cron:
    - web
    - file
    - no_mcp

hermes tools list --platform cron marked web and file enabled and marked the other built-in toolsets disabled. It did not print no_mcp. Under a separate heading, MCP servers, it printed four lines:

gauge  all tools enabled
quiet  all tools enabled
word_off  all tools enabled
word_nope  all tools enabled

The status column in the real output used a check or a cross. Those four MCP lines did not. all tools enabled is the tool filter. The printer looks at tools.include and tools.exclude. None of these blocks had a tools filter, so every block got that sentence, including quiet, whose enabled flag was false. The sentence is not the enabled flag, and it is not the cron allowlist. The same four lines were printed for --platform cli. The MCP heading is the whole mcp_servers map, not a per-platform selection.

The toolset section of that list is also a different call from the one the scheduler makes. The list path asks for platform tools with default MCP servers left out. The cron resolver asks for the same platform and leaves that default on. On this file, before the disable, the list-shaped view of the cron platform was file and web. The run-shaped view was also file and web, because no_mcp was still in the saved list and the sentinel strips the servers. The two views agreed only while the sentinel was present. The list still did not show the sentinel, so the agreement was not visible in the command output.

hermes tools list --platform cli, on a home with no saved CLI list, marked the broad default set enabled, including terminal, browser, and cronjob. The cron list did not. The two platforms are separate checklists. The cron page is right that the cron agent does not inherit the CLI checklist. The missing part is that neither checklist is the set of names the constructor receives once an MCP server is enabled and the sentinel is absent.

Disable removes the sentinel

vision was already absent from the cron list. The command was still:

hermes tools disable vision --platform cron

It exited 0 and printed Disabled: vision. The cron platform list in the file became:

platform_toolsets:
  cron:
    - file
    - web

no_mcp was gone. vision was still absent, which is what a disable of an already-disabled name should do. The rewrite did more than that. Saving the platform list drops no_mcp rather than preserving it. The same write recorded vision under known_builtin_toolsets.cron. That key is the checklist memory, the names the picker has offered. It is not the allowlist. A search of the file for vision after this command hits that record and misses the enabled list.

The file’s platform_toolsets map contained only cron after the write. This disable did not materialize a CLI list. The help text for hermes tools disable still defaults --platform to cli. A disable without the flag would have written the other platform. This run passed --platform cron and still lost the sentinel.

After that write, the two views of the cron platform diverged. The list-shaped view was file and web. The run-shaped view was file, gauge, web, and word_nope. hermes tools list --platform cron still marked only web and file enabled, and it still printed all tools enabled for all four servers, including the two the resolver was not adding. The command that is supposed to show the cron platform cannot show the names the run adds, and it cannot show that the opt-out was deleted.

A job pin does not close the same hole

A per-job list is the other control the cron page describes. On the same four server blocks, these stored values resolved as follows.

A stored list of web and file resolved to web, file, gauge, word_nope. The native names stayed in the order they were stored. The enabled server names were appended in sorted order. terminal and browser were not added. The page’s comment about those native toolsets held. The MCP names were the addition the comment does not mention.

A stored list of web and gauge resolved to web and gauge. Naming one enabled server made that name the server allowlist. word_nope was not added. The pin is narrow for servers only when it already names a server, or when it opts out.

A stored list of web, file, and no_mcp resolved to web and file. The sentinel was stripped. It does not appear in the list the constructor receives, and it does not appear in hermes tools list. Its effect is the absence of the server names.

A stored empty list resolved to an empty list. No server name was merged back in. An empty list is a zero-toolset allowlist, not a request for the platform default. A missing key is not an empty list. A JSON null is not an empty list. Both of those fell through to the cron platform run view. After the sentinel had been removed, that view was file, gauge, web, and word_nope.

The disabled list passed beside the enabled list was cronjob, messaging, and clarify. Those three names are the cron session’s own denylist on a config that does not set agent.disabled_toolsets and does not turn on agent scheduling. gauge and word_nope were not in it. The denylist does not cancel the merge. This run called the two functions the constructor call site calls. It did not construct the agent, so it does not show a later filter inside the agent class. The arguments that call site would pass, on this config, already included the server names in the enabled argument and did not include them in the disabled argument.

The job the CLI actually wrote

hermes cron create has no flag for enabled_toolsets. The job was created paused, with delivery local, schedule 0 9 * * *, and a one-line prompt. The create output said the job was paused and that no gateway was serving the isolated profile. That warning is why the job could be created without a scheduler attached. The job file then held "enabled_toolsets": null and "state": "paused".

hermes cron list printed the name, the schedule, paused, and local. It did not print toolsets. hermes cron doctor exited 0, printed that it found no issues, and printed that no active jobs were configured. A paused job is outside the active set that sentence is about. The clean doctor result is not a statement about the allowlist.

Calling the resolver on that job object, against the config after the disable, returned file, gauge, web, and word_nope. The stored null is why. A job the CLI creates does not get a narrow pin. It inherits the cron platform run view, and that view includes every enabled MCP server once no_mcp is absent. Leaving the job paused was the point. Firing it would have been a different test, and this profile had no gateway to fire it.

Verify the resolved list

Do not treat hermes tools list, hermes cron list, or hermes cron doctor as the allowlist check. On this version the first shows the checklist and the tool filter. The second shows schedule state. The third, on this paused job, reported no issues. The names the constructor receives were in none of those outputs.

Read the job file for enabled_toolsets. Null and a missing key are the platform path. An empty array is zero tools. A non-empty array that does not contain no_mcp and does not name a server still receives every server the enabled-flag reader accepts. Then read platform_toolsets.cron the same way. If no_mcp is not in that list, the platform path has the same hole.

The check that matched the scheduler, in this checkout, was a short script run with HERMES_HOME pointed at the home under test. It loaded that home’s config and called _resolve_cron_enabled_toolsets on the job dict. The import path was the checkout that hermes --version identified. Compare the returned list with the stored list. The difference is the set a narrow pin does not keep out.

To keep the servers out, put no_mcp on the list you intend to be authoritative, either the job’s enabled_toolsets or platform_toolsets.cron if the job key is null. After any hermes tools disable or hermes tools enable on that platform, read the file again. This run’s disable of an already-disabled toolset deleted the sentinel and left a success line. If you need one server and no others, name that server in the job list. Naming gauge kept word_nope out. An empty job list also kept every server out, and it kept the native toolsets out too. Use that only when the job should have no tools.

enabled: false or the string off kept a block out of the enabled set. Omitting the key did not. A string the reader does not recognize did not. It warned and counted the server as on. After changing a flag, resolve again. The list command will still say all tools enabled for a block that the resolver rejects, and it will still say that for a block the resolver accepts. The sentence cannot make the distinction.

This run did not attach a live server, so it does not show whether a name in the resolved list becomes a callable tool or an error at the first call. The boundary it does show is earlier. The saved checklist and the job file can both look limited while the constructor argument already names the servers. On 0.22.5 that argument is the list to review before an unattended job is allowed to run.

Pages and output used for this check

The cron page is https://hermes-agent.nousresearch.com/docs/user-guide/features/cron, section “Toolsets available to cron jobs”, fetched 16 November 2026. The preflight paragraph on that page says a job is checked for MCP servers named in its own enabled_toolsets. It does not describe servers added by the resolver. The list and disable help text is hermes tools list --help and hermes tools disable --help from the same 0.22.5 binary. The resolved lists, the warning line, the rewritten platform list, and the paused job file are from the isolated home described above.