get_document_path

What get_document_path does on Aos

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

Why get_document_path is rated Low

This tool performs a read-only operation—it retrieves and returns the file path of an open document. There are no side effects, no code execution, and no data modification. The blast radius of misuse is minimal, as an attacker could only learn the file system location of the Rhino document, which is low-impact information disclosure. Confidence is high because the description is explicit and unambiguous.

From the tool's definition Tool name 'get_document_path' and description 'Return the file path of the currently open Rhino document' indicate a simple query operation that retrieves metadata about the current document without modifying, executing, or deleting anything.

The rule that runs get_document_path safely

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

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

Questions about get_document_path