Skip to main content
Glama

rush_security

Scan project dependencies at a given path for known vulnerabilities with pip-audit for Python and npm audit for JS/TS. Returns status, findings, and summary to help fix security issues.

Instructions

Scan deps at for known vulnerabilities. Returns {status, findings[], summary}. Engines: pip-audit (Python), npm audit (JS/TS). status='skipped' means engine not on PATH.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
allow_slowNo
allow_buildNo
allow_browserNo
allow_networkNo
allow_downloadNo
allow_cache_writeNo
allow_artifact_writeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
rawNo
toolNo
engineNo
statusNo
metricsNo
summaryNo
findingsNo
metadataNo
artifactsNo
duration_msNo
review_kindNo
engine_versionNo
review_providerNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.3.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It adds useful details: supported engines (pip-audit, npm audit), return shape, and status='skipped' semantics. However, it does not disclose side effects, network usage, or what the allow_* flags control, which is a meaningful gap for a tool with no annotation safety hints.

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

Conciseness5/5

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

The description uses three terse sentences, front-loading the core purpose, then including the return shape, supported engines, and a special status meaning. There is no fluff and every sentence earns its place.

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

Completeness2/5

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

The tool has eight parameters, no per-parameter schema descriptions, and no annotations, yet the description only documents path and engine behavior. The allow_* flags, which likely gate slow/network/build/cache operations, are unexplained, so an agent cannot fully understand what invoking the tool with defaults will do.

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

Parameters1/5

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

Schema description coverage is 0%, and the description only adds meaning to 'path' via 'deps at <path>'. The seven allow_* boolean parameters are entirely unexplained in both the schema and the description, leaving an agent to guess their purpose.

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?

The description states a specific verb and resource: 'Scan deps at <path> for known vulnerabilities.' This clearly identifies the tool's function and distinguishes it from adjacent siblings like rush_sbom or rush_secrets by targeting dependency vulnerability scanning.

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

Usage Guidelines2/5

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

No guidance is provided for when to use rush_security over sibling tools such as rush_sbom or rush_secrets, and no exclusions or prerequisites are mentioned. The engine list hints at supported ecosystems but does not help an agent decide when this tool is the right choice.

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

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/jamesdsizemore/rush-cli'

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