Introduction

In DeepSeek Harness (DSH) development, the safety and correctness of agent behavior heavily depend on the configuration of the “tool surface.” When assembling a bundle, developers may unintentionally expose code execution interfaces or side-effect tools that should not be accessible to the model. dsh-agent-doctor is designed to address this configuration audit pain point by statically checking the currently effective tool surface through a diagnostic command.

Plugin Introduction

This is a lightweight DSH health and safety diagnostic plugin maintained by user MkaliezZ. It uses the /doctor command to inspect the effective model-visible tool surface of the Agent and report boundary configuration signals. The plugin itself does not claim to act as antivirus software, a malware scanner, a sandbox, or a policy enforcement boundary.

Core Features

The plugin provides the following checks:
1. Tool inventory statistics: Reports the number of tools currently visible to the model and their specific names.
2. Reserved interface visibility: Checks whether the retained run_code interface is visible to the model.
3. Heuristic warnings: Issues prompts for tools whose names clearly indicate side-effect tendencies (advisory only, not blocking).
4. AgentFuse check (optional): Confirms whether AgentFuse is present.
5. Approval service signals (optional): Detects whether an approval service is available.

Installation and Activation

This plugin is designed to be mounted as a DSH bundle. Add the following snippet to the DSH configuration file to enable it:

- id: dsh-agent-doctor
  name: '@mkaliezz/dsh-agent-doctor'
  config:
    requireAgentFuse: false

Typical Usage

After completing bundle assembly in the DSH interactive interface, enter the /doctor command directly to trigger diagnostics and view the report.

Use Cases and Cautions

  • Use cases: For confirming whether an Agent’s tool chain includes interfaces that should not be exposed (such as code executors), or for developers relying on AgentFuse for hybrid orchestration.
  • Cautions:
    • This plugin runs with the permissions of the current DSH process and is not a process sandbox or policy enforcement boundary.
    • It is not antivirus software or a malware scanner.
    • It cannot prove the safety of a tool based on its name alone.
    • It cannot prove the immutability of the effective configuration.
    • Review the source code and license before use.

Conclusion

This plugin is suitable as a configuration audit assistant in a DSH environment, helping developers manage tool surface visibility. The plugin directory and source repository are as follows: