Low Risk

analyze_module_structure

Analyze the structure of a module/file

How to control analyze_module_structure ↓

What analyze_module_structure does on CodeGraphMCPServer

AI agents call analyze_module_structure to retrieve information from CodeGraphMCPServer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why analyze_module_structure needs a policy

This tool retrieves and analyzes structural information about code modules/files without executing code, modifying files, or triggering external operations. It is purely introspective and has no side effects. The use of 'analyze' in a code analysis context means examining/understanding, not transforming or executing. Therefore it is classified as Read with low severity and high confidence.

From the tool's definition Tool name 'analyze_module_structure' and description 'Analyze the structure of a module/file' indicate a query/inspection operation with no modification or execution of code.

Documented attack patterns abuse exactly the kind of access analyze_module_structure gives an agent:

How to control analyze_module_structure

PolicyLayer is an MCP gateway — it sits between your AI agents and CodeGraphMCPServer, and nothing reaches the server without passing your rules. This is the rule we recommend for analyze_module_structure:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "analyze_module_structure": {}
  }
}

analyze_module_structure is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register CodeGraphMCPServer — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about analyze_module_structure

What does the analyze_module_structure tool do? +

Analyze the structure of a module/file. It is categorised as a Read tool in the CodeGraphMCPServer MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on analyze_module_structure? +

Register the CodeGraphMCPServer MCP server in PolicyLayer and add a rule for analyze_module_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 CodeGraphMCPServer. Nothing to install.

What risk level is analyze_module_structure? +

analyze_module_structure is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit analyze_module_structure? +

Yes. Add a rate_limit block to the analyze_module_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.

How do I block analyze_module_structure completely? +

Set action: deny in the PolicyLayer policy for analyze_module_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.

What MCP server provides analyze_module_structure? +

analyze_module_structure is provided by the CodeGraphMCPServer MCP server (nahisaho/codegraphmcpserver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every CodeGraphMCPServer tool call.

Start from CodeGraphMCPServer, 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.

14 CodeGraphMCPServer tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.