Inspect Hermes Agent MCP Server Exposure in a Disposable Profile

Audit Hermes as a source of MCP tools before giving another client access. The operator should understand what the client can read or invoke after discovery, especially when a profile holds messaging conversations or account credentials.

  1. Isolated profile
  2. Discover MCP tools
  3. Review capability exposure
Isolated profile → Discover MCP tools → Review capability exposure

Build an empty test boundary

Create an isolated, disposable Hermes profile with no connected messaging accounts or production provider credentials. Verify the current official mcp-serve marketplace documentation and follow its plugin installation directions only in that test profile. Check the installed help for the documented command hermes mcp-serve. Preserve the selected profile in the client's launch configuration. An executable started without the intended profile can use the default profile.

Using a trusted MCP inspector or client, start the server over stdio, complete initialize and then request tools/list. Record the names and descriptions. Compare them to an allowlist defined by your deployment requirements. Inspect descriptions and input schemas before any tool invocation. This audit requires discovery only. Leave network-capable tool exposure off for the first trial.

The official plugin description states that conversation operations can include reading, sending messages and answering approvals. Treat the interface as privileged even when the optional --tools switch is absent. The switch expands optional exposed tools. Review the installed command and actual discovery output to verify the boundary for your version.

Analyze and test the allowlist

Keep a small fixture containing permitted names and rationale. Fail the audit when an unexpected write, message, approval or data-reading tool appears. Repeat against a snapshot of discovery output after an upgrade. A tool disappearing may break a client, so report missing expected tools as well. Avoid logging arguments, conversation content or secret-bearing environment variables while inspecting.

A safe failure drill is to place a synthetic unexpected tool name into a copy of the discovery listing and verify that your review marks it as blocked. A manual discovery review remains important because a stable tool name can gain new behavior through changing parameters or implementation.

Is mcp-serve the same as configuring Hermes to call an external MCP server? Here the external client connects to Hermes and receives Hermes capabilities. The opposite direction lets Hermes consume another system's tool list.

Can the client prevent all unintended access just by hiding a tool? Apply credential and profile isolation on the server side. Treat client-side visibility as an additional control.

References

Official Hermes Agent documentation · ASP.NET PB on MCP tools and resources

Comments