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

quality_run_security_scan

Ejecuta bandit. 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-run-security-scan.md

What quality_run_security_scan does on MCP Framework Personal

AI agents invoke quality_run_security_scan 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_run_security_scan is rated High

This tool executes an external security scanning tool (bandit) whose behavior depends on the target argument provided. While bandit itself is non-destructive, executing code analysis tools qualifies as Execute category because it triggers external operations with effects that depend on user-supplied arguments.

From the tool's definition Tool description states 'Ejecuta bandit' (Executes bandit), where bandit is a Python security scanning tool that runs code analysis. The tool accepts a target parameter (directory, default all), indicating it executes bandit against arbitrary code paths.

Questions about quality_run_security_scan

What does the quality_run_security_scan tool do? +

Ejecuta bandit. 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_run_security_scan? +

Register the MCP Framework Personal MCP server in PolicyLayer and add a rule for quality_run_security_scan: 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_run_security_scan? +

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

Can I rate-limit quality_run_security_scan? +

Yes. Add a rate_limit block to the quality_run_security_scan 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_run_security_scan completely? +

Set action: deny in the PolicyLayer policy for quality_run_security_scan. 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_run_security_scan? +

quality_run_security_scan 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.