Skip to main content
Glama
balasriharsha

shieldbot

by balasriharsha
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
scan_repositoryA

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.

check_scanner_toolsA

Check which security scanner tools are installed and available.

Returns a JSON object mapping each tool name to its availability status and install path (or install instructions if missing).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored across 2 tools

Disambiguation5/5

The two tools are completely distinct: one checks which scanners are installed, the other runs a full security scan. There is no overlap or confusion between them.

Naming Consistency5/5

Both tool names follow a consistent verb_noun pattern (check_scanner_tools, scan_repository), making the purpose clear and predictable.

Tool Count3/5

With only 2 tools, the server feels thin for the domain of security scanning. While the core actions are covered, additional tools for viewing scan history or configuring scans would be expected.

Completeness2/5

The server lacks tools for retrieving previous scan results, managing scan configurations, or listing repositories. Agents can check scanner availability and run a scan, but cannot access past reports or manage scan lifecycle.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources