Get the structure of a GitHub repository
AI agents call get-repo-structure to retrieve information from GitHub Repository MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns repository structure metadata (file tree, directory layout, paths) without modifying, executing, or deleting anything. It is purely informational. Severity is medium rather than low because repository structure can reveal architectural details, internal organization, and file paths that might aid reconnaissance in a multi-step attack, but the tool itself causes no direct harm.
From the tool's definition Tool description states it 'Get[s] the structure of a GitHub repository' — a retrieval operation with no modification.
Attacks that exploit this kind of access
Get the structure of a GitHub repository. It is categorised as a Read tool in the GitHub Repository MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub Repository MCP Server MCP server in PolicyLayer and add a rule for get-repo-structure: 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 GitHub Repository MCP Server. Nothing to install.
get-repo-structure 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-repo-structure 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-repo-structure. 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-repo-structure is provided by the GitHub Repository MCP Server MCP server (shanksxz/gh-mcp-server). 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 →