quality_find_dead_code
Ejecuta vulture. Parametros: target (directorio, default todo).
This record as markdown: /tools/inggerman-mcps/quality-find-dead-code.md
What quality_find_dead_code does on MCP Framework Personal
AI agents invoke quality_find_dead_code to trigger actions in MCP Framework Personal. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why quality_find_dead_code is rated High
The tool executes an external program (vulture) to perform dead code analysis. This is an Execute category action as it runs an external tool/command. The severity is medium because while it is read-only in intent (static analysis), executing arbitrary tools against a directory could have unintended side effects depending on the environment, and the target parameter could potentially be misused to point at sensitive…
From the tool's definition 'Ejecuta vulture' (Executes vulture) — the tool runs an external static analysis tool (vulture) against a target directory
Attacks that exploit this kind of access
The rule that runs quality_find_dead_code 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 quality_find_dead_code, this is the rule to start with:
quality_find_dead_code stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 quality_find_dead_code call is checked against it from then on.
Questions about quality_find_dead_code
Ejecuta vulture. Parametros: target (directorio, default todo). It is categorised as a Execute tool in the MCP Framework Personal MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Framework Personal MCP server in PolicyLayer and add a rule for quality_find_dead_code: 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.
quality_find_dead_code is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the quality_find_dead_code 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 quality_find_dead_code. 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.
quality_find_dead_code 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.
Across the catalogue