⭐ PREFERRED OVER ls/tree: Get clean repository structure showing directories and file types. Use this INSTEAD OF running ls, tree, or Glob for understanding project layout. No file contents, just structure.
AI agents call get_repository_structure to retrieve information from MCP Context Manager without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves metadata about repository organization (directories and file types) without executing code, modifying data, deleting anything, or triggering external operations. It has no side effects and returns informational data only. The emphasis on using it INSTEAD OF ls/tree further confirms it is a passive structural query.
From the tool's definition Tool description states 'Get clean repository structure showing directories and file types' with 'No file contents, just structure.' This is a read-only retrieval operation analogous to `ls` or `tree` commands.
Documented attack patterns abuse exactly the kind of access get_repository_structure gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Context Manager, and nothing reaches the server without passing your rules. This is the rule we recommend for get_repository_structure:
{
"version": "1",
"default": "deny",
"tools": {
"get_repository_structure": {}
}
}get_repository_structure 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.
⭐ PREFERRED OVER ls/tree: Get clean repository structure showing directories and file types. Use this INSTEAD OF running ls, tree, or Glob for understanding project layout. No file contents, just structure. It is categorised as a Read tool in the MCP Context Manager MCP Server, which means it retrieves data without modifying state.
Register the MCP Context Manager MCP server in PolicyLayer and add a rule for get_repository_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 MCP Context Manager. Nothing to install.
get_repository_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_repository_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_repository_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_repository_structure is provided by the MCP Context Manager MCP server (transparentlyok/mcp-context-manager). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Context Manager, 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.
21 MCP Context Manager tools catalogued and risk-classified — across an index of 43,000+ MCP servers.