arch_detect_code_smells
Detecta code smells en un archivo. Parametros: target_file (requerido).
This record as markdown: /tools/inggerman-mcps/arch-detect-code-smells.md
What arch_detect_code_smells does on MCP Framework Personal
AI agents call arch_detect_code_smells 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_detect_code_smells is rated Low
Code smell detection is a read-only static analysis operation that analyzes file contents to identify potential code quality issues. It does not modify files, execute code, delete data, or trigger external side effects—it merely queries and reports findings. This qualifies as a Read category tool with low severity since misuse would at worst produce false analysis reports rather than cause harm.
From the tool's definition Tool name 'arch_detect_code_smells' and description 'Detecta code smells en un archivo' (Detects code smells in a file) indicate static analysis of code. The required parameter is 'target_file', suggesting file inspection without modification.
Attacks that exploit this kind of access
The rule that runs arch_detect_code_smells 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_detect_code_smells, this is the rule to start with:
arch_detect_code_smells 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_detect_code_smells call is checked against it from then on.
Questions about arch_detect_code_smells
Detecta code smells en un archivo. Parametros: target_file (requerido). 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_detect_code_smells: 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_detect_code_smells 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_detect_code_smells 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_detect_code_smells. 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_detect_code_smells 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