Skip to main content
Glama
balasriharsha

shieldbot

scan_repository

Run a comprehensive security scan on a repository using multiple parallel scanners to detect vulnerabilities, secrets, and dependency CVEs, and receive a deduplicated severity-ranked report.

Instructions

Run a full security scan on a repository.

Executes the following scanners in parallel:

  • CodeQL (deep dataflow / taint-analysis SAST, open-source CLI)

  • Semgrep (5,000+ OWASP/CWE rules)

  • bandit (Python-specific security linter)

  • ruff (Python quality + security patterns)

  • detect-secrets / gitleaks (hardcoded secrets)

  • osv-scanner / dependabot (dependency CVEs via OSV/GHSA advisory DB)

  • pip-audit (Python CVEs)

  • npm-audit (Node.js CVEs)

  • trivy (Docker image CVEs, misconfigurations, and baked-in secrets — runs when a Dockerfile is found)

Returns a JSON report with deduplicated, severity-ranked findings.

Args: repo_path: Absolute or relative path to the repository to scan. skip_scanners: Optional list of scanner names to skip. Valid values: codeql, semgrep, bandit, ruff, detect-secrets, dependabot, pip-audit, npm-audit, trivy scan_git_history: If True, scan git history for leaked secrets (requires gitleaks to be installed). extra_images: Pre-built Docker image names/tags to scan directly with Trivy. Use when docker build fails in a restricted environment. Example: ["mcr.microsoft.com/playwright:v1.50-noble"]

Returns: JSON string containing the full SecurityReport with all findings, per-scanner metadata, severity counts, and scan duration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repo_pathYes
skip_scannersNo
scan_git_historyNo
extra_imagesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, but description fully discloses parallel execution, return format, conditions for Trivy, and parameter effects. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is comprehensive but slightly lengthy; front-loaded with purpose but lists scanners in a verbose manner. Each sentence provides value, though some redundancy exists.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, 4 parameters, and existence of output schema, description covers all necessary context: scanner list, parameter options, edge cases (Dockerfile trigger).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, yet description explains all parameters: repo_path, skip_scanners with valid values, scan_git_history with requirement, extra_images with example.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the tool runs a full security scan on a repository, listing specific scanners. Distinguishes from sibling tool 'check_scanner_tools' by focusing on scanning execution.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains the tool's role and customization via skip_scanners, but does not explicitly state when not to use it or recommend alternatives beyond the sibling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/balasriharsha/shieldbot'

If you have feedback or need assistance with the MCP directory API, please join our Discord server