Analyze project structure, dependencies, and metrics
AI agents call analyze_project_structure to retrieve information from Claude MCP Server Integration without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and examines project metadata (structure, dependencies, metrics) without creating, modifying, executing, or deleting anything. It is a pure analysis/inspection tool with no side effects, fitting the Read category. Low severity because misuse would only expose information about the project, not cause damage or execute code.
From the tool's definition Tool name 'analyze_project_structure' and description 'Analyze project structure, dependencies, and metrics' indicate data retrieval and analysis only.
Attacks that exploit this kind of access
Analyze project structure, dependencies, and metrics. It is categorised as a Read tool in the Claude MCP Server Integration MCP Server, which means it retrieves data without modifying state.
Register the Claude MCP Server Integration MCP server in PolicyLayer and add a rule for analyze_project_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 Claude MCP Server Integration. Nothing to install.
analyze_project_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_project_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_project_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_project_structure is provided by the Claude MCP Server Integration MCP server (mokemoke0821/claude-mcp-integration). 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 →