arch_analyze_dependencies
Usa AST para extraer todas las importaciones de un archivo .py y entender su acoplamiento.
This record as markdown: /tools/inggerman-mcps/arch-analyze-dependencies.md
What arch_analyze_dependencies does on MCP Framework Personal
AI agents call arch_analyze_dependencies to retrieve information from MCP Framework Personal without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why arch_analyze_dependencies is rated Low
The tool uses AST (Abstract Syntax Tree) parsing to extract and analyze import dependencies from a Python file. This is a read-only static analysis operation with no side effects. Severity is medium because it reads source code files which could expose sensitive logic or architecture details if misused.
From the tool's definition 'extraer todas las importaciones de un archivo .py' (extract all imports from a .py file) and 'entender su acoplamiento' (understand its coupling) — purely analytical/read operation using AST parsing
Attacks that exploit this kind of access
The rule that runs arch_analyze_dependencies safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Framework Personal, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For arch_analyze_dependencies, this is the rule to start with:
arch_analyze_dependencies is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect MCP Framework Personal, apply this rule, and every arch_analyze_dependencies call is checked against it from then on.
Questions about arch_analyze_dependencies
Usa AST para extraer todas las importaciones de un archivo .py y entender su acoplamiento. It is categorised as a Read tool in the MCP Framework Personal MCP Server, which means it retrieves data without modifying state.
Register the MCP Framework Personal MCP server in PolicyLayer and add a rule for arch_analyze_dependencies: 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 Framework Personal. Nothing to install.
arch_analyze_dependencies 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 arch_analyze_dependencies 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 arch_analyze_dependencies. 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.
arch_analyze_dependencies is provided by the MCP Framework Personal MCP server (inggerman/mcps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP Framework Personal, and thousands of servers like it.
This server
Across the catalogue