workspace_read_file

What workspace_read_file does on Hercules MCP

AI agents call workspace_read_file to retrieve information from Hercules MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why workspace_read_file is rated Low

The tool retrieves file contents without side effects. However, severity is elevated from 'low' to 'medium' because: (1) the container runs Kali Linux with offensive security tools, and an AI agent could read sensitive files like credentials, keys, or payloads stored in the workspace; (2) in a penetration testing context, reading tool outputs or configuration files could expose attack strategies or reconnaissance…

From the tool's definition Tool description states 'Read the contents of a file inside the container workspace' — a straightforward read operation with no write or destructive capability.

The rule that runs workspace_read_file safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Hercules MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For workspace_read_file, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "workspace_read_file": {}
  }
}

Questions about workspace_read_file