Get the full hierarchy of the Roblox place — scripts, models, folders, services. Returns a tree structure showing every instance and its children. Use this as your first call to understand the project layout. Tip: Use depth=2 or depth=3 for large places to keep output manageable. Args: - path (st...
AI agents call get_file_tree to retrieve information from Melo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays the structural layout of a Roblox place without side effects. It is a read-only query operation that returns hierarchical data for inspection purposes. The optional depth parameter is for filtering output volume, not changing behavior. No data is modified, deleted, or executed.
From the tool's definition Tool description states 'Get the full hierarchy' and 'Returns a tree structure showing every instance and its children' — pure information retrieval with no modification, deletion, or execution capability.
Risk signalsBulk/mass operation — affects multiple targets · Admin/system-level operation
Attacks that exploit this kind of access
Get the full hierarchy of the Roblox place — scripts, models, folders, services. Returns a tree structure showing every instance and its children. Use this as your first call to understand the project layout. Tip: Use depth=2 or depth=3 for large places to keep output manageable. Args: - path (string, optional): Root path to start from (default:. It is categorised as a Read tool in the Melo MCP Server, which means it retrieves data without modifying state.
Register the Melo MCP server in PolicyLayer and add a rule for get_file_tree: 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 Melo. Nothing to install.
get_file_tree 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 get_file_tree 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 get_file_tree. 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.
get_file_tree is provided by the Melo MCP server (yannyhl/linkedsword-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 →