New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

quality_find_dead_code

Ejecuta vulture. Parametros: target (directorio, default todo).

SERVERMCP Framework Personal SOURCEinggerman/mcps
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

Questions about quality_find_dead_code

What does the quality_find_dead_code tool do? +

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.

How do I enforce a policy on quality_find_dead_code? +

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.

What risk level is quality_find_dead_code? +

quality_find_dead_code is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit quality_find_dead_code? +

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.

How do I block quality_find_dead_code completely? +

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.

What MCP server provides quality_find_dead_code? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of MCP Framework Personal's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.