Local directory tree inspection. Orient at root first, then drill into source/package dirs. Tree shape separates implementation from tests, examples, fixtures, docs, and generated output. Follow up with localSearchCode for content or localGetFileContent for specific files.
AI agents call localViewStructure to retrieve information from Octocode MCP - AI Context Platform without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
queries | array | Yes | Array of queries for localViewStructure. Maximum is 5 queries per call. Multiple queries run in parallel. Use the per-query `page` field to navigate through res |
Parameters from the server's own tool schema.
This tool only retrieves and displays directory structure information. It has no capability to modify, delete, create, or execute operations. The blast radius of misuse is minimal—an attacker could gain knowledge of code organization but cannot alter files or trigger execution. This is a classic Read operation.
From the tool's definition 'Local directory tree inspection' and 'Orient at root first, then drill into source/package dirs' indicates retrieval of filesystem directory structure without modification.
Risk signalsAccepts file system path (queries[].path) · High parameter count (20 properties) · Admin/system-level operation
Documented attack patterns abuse exactly the kind of access localViewStructure gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Octocode MCP - AI Context Platform, and nothing reaches the server without passing your rules. This is the rule we recommend for localViewStructure:
{
"version": "1",
"default": "deny",
"tools": {
"localViewStructure": {}
}
}localViewStructure is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Local directory tree inspection. Orient at root first, then drill into source/package dirs. Tree shape separates implementation from tests, examples, fixtures, docs, and generated output. Follow up with localSearchCode for content or localGetFileContent for specific files. It is categorised as a Read tool in the Octocode MCP - AI Context Platform MCP Server, which means it retrieves data without modifying state.
localViewStructure accepts 1 parameter: queries. Required: queries. The full parameter table on this page comes from the server's own tool schema.
Register the Octocode MCP - AI Context Platform MCP server in PolicyLayer and add a rule for localViewStructure: 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 Octocode MCP - AI Context Platform. Nothing to install.
localViewStructure 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 localViewStructure 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 localViewStructure. 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.
localViewStructure is provided by the Octocode MCP - AI Context Platform MCP server (octocode-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Octocode MCP - AI Context Platform, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 Octocode MCP - AI Context Platform tools catalogued and risk-classified — across an index of 43,000+ MCP servers.