Find a WizTree executable using WIZTREE_PATH, PATH, and common install folders.
AI agents call locate_wiztree to retrieve information from WizTree MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a path-discovery utility that locates an existing executable. It performs read-only filesystem queries (checking directories and environment variables) with no side effects, data modification, or external execution. It falls cleanly under the Read category.
From the tool's definition Tool name and description indicate it 'Find[s] a WizTree executable' by searching environment variables and common install folders. No data modification, deletion, or external command execution occurs—only lookup and discovery of file system paths.
Attacks that exploit this kind of access
Find a WizTree executable using WIZTREE_PATH, PATH, and common install folders. It is categorised as a Read tool in the WizTree MCP MCP Server, which means it retrieves data without modifying state.
Register the WizTree MCP server in PolicyLayer and add a rule for locate_wiztree: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches WizTree MCP. Nothing to install.
locate_wiztree is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the locate_wiztree rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for locate_wiztree. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
locate_wiztree is provided by the WizTree MCP server (onmokoworks/wiztree-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →