Analyze the package structure of a repository
AI agents call analyze_package_structure to retrieve information from MCP Code Analysis 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 examines code organization/structure metadata to provide insights. It has no side effects, does not execute code, does not modify any data, and does not delete anything. It is a safe informational query similar to other read-only tools on the server like 'analyze_file', 'explain_code', and 'detect_anti_patterns' which are all analytical in nature.
From the tool's definition Tool name 'analyze_package_structure' and description 'Analyze the package structure of a repository' indicate a purely analytical operation that queries and examines existing code structure without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access analyze_package_structure gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Code Analysis Server, and nothing reaches the server without passing your rules. This is the rule we recommend for analyze_package_structure:
{
"version": "1",
"default": "deny",
"tools": {
"analyze_package_structure": {}
}
}analyze_package_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.
Analyze the package structure of a repository. It is categorised as a Read tool in the MCP Code Analysis Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Code Analysis Server MCP server in PolicyLayer and add a rule for analyze_package_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 Code Analysis Server. Nothing to install.
analyze_package_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 analyze_package_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 analyze_package_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.
analyze_package_structure is provided by the MCP Code Analysis Server MCP server (johannhartmann/mcpcodeanalysis). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Code Analysis Server, 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.
44 MCP Code Analysis Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.