ToolTrust
A4/100
runpod

runpod-runpod-mcp-ts

mcp1.1.0

@runpod

By runpod | 73 findings | Scanned 10/15/2026 | tooltrust-scanner/v0.3.20 | 85

Repository health

Popularity and maintenance signals alongside the security grade.

View repository
Stars

85

current snapshot

Forks

23

current snapshot

Contributors

15

public GitHub contributors

Last commit

Oct 23, 2026

GitHub repository activity

Last release

Oct 23, 2026

v4.6.0

Release version

v4.6.0

Latest GitHub release

Stars trend

Daily star additions · githubarchive_bq · observed through Oct 22, 2026 · export updated Oct 26, 2026

—

No observed star events yet.

——

Pull request activity

Weekly PR events · githubarchive_bq · observed through Oct 22, 2026 · export updated Oct 26, 2026

2026-09-142026-10-19

Data quality: observed_events. Charts show observed events, not a reconstructed historical total.

TypeScriptNOASSERTIONDeveloper Tools46.9k/mo npm downloadsLast scan Oct 15, 2026
5 Low68 Info

Risk Summary

Safe With Normal Controls

Missing Description is the main signal, but overall risk remains within an acceptable range.

Potential impact: This finding indicates the tool should be reviewed before it is trusted.

Recommended action: No high-risk findings were detected in this scan, but you should still apply least-privilege defaults and rescan after changes.

Suggested policy: keep this tool behind manual approval, do not allow unattended runs, and re-scan after narrowing risky permissions.

Security Findings (73)

  • LowAS-002

    ⚠️Excessive Permissions ×2

    input schema exposes 11 properties (threshold: 10)

    create-podcreate-template

    Fix: Tool requests broad permissions (exec/fs/network). Validate input parameters using Enums where possible, and restrict file system operations to explicit allowed directories.

  • LowAS-011

    ℹ️Missing Rate-Limit / Timeout ×3

    tool performs network or execution operations but declares no rate-limit, timeout, or retry configuration

    get-endpointdelete-endpointcreate-template

    Fix: Declare explicit rate-limit, timeout, and retry configuration for all network and execution tools. Implement exponential back-off and surface resource state to the calling agent.

  • InfoAS-007

    ℹ️Missing Description or Schema ×26

    Tool 'list-pods' has no description - agents cannot reason about its purpose, and static analysis coverage is limited

    list-pods

    Tool 'get-pod' has no description - agents cannot reason about its purpose, and static analysis coverage is limited

    get-pod

    Tool 'create-pod' has no description - agents cannot reason about its purpose, and static analysis coverage is limited

    create-pod

    Tool 'update-pod' has no description - agents cannot reason about its purpose, and static analysis coverage is limited

    update-pod

    Tool 'start-pod' has no description - agents cannot reason about its purpose, and static analysis coverage is limited

    start-pod

    Tool 'stop-pod' has no description - agents cannot reason about its purpose, and static analysis coverage is limited

    stop-pod

    Tool 'delete-pod' has no description - agents cannot reason about its purpose, and static analysis coverage is limited

    delete-pod

    Tool 'list-endpoints' has no description - agents cannot reason about its purpose, and static analysis coverage is limited

    list-endpoints

    Tool 'get-endpoint' has no description - agents cannot reason about its purpose, and static analysis coverage is limited

    get-endpoint

    Tool 'create-endpoint' has no description - agents cannot reason about its purpose, and static analysis coverage is limited

    create-endpoint

    Tool 'update-endpoint' has no description - agents cannot reason about its purpose, and static analysis coverage is limited

    update-endpoint

    Tool 'delete-endpoint' has no description - agents cannot reason about its purpose, and static analysis coverage is limited

    delete-endpoint

    Tool 'list-templates' has no description - agents cannot reason about its purpose, and static analysis coverage is limited

    list-templates

    Tool 'get-template' has no description - agents cannot reason about its purpose, and static analysis coverage is limited

    get-template

    Tool 'create-template' has no description - agents cannot reason about its purpose, and static analysis coverage is limited

    create-template

    Tool 'update-template' has no description - agents cannot reason about its purpose, and static analysis coverage is limited

    update-template

    Tool 'delete-template' has no description - agents cannot reason about its purpose, and static analysis coverage is limited

    delete-template

    Tool 'list-network-volumes' has no description - agents cannot reason about its purpose, and static analysis coverage is limited

    list-network-volumes

    Tool 'get-network-volume' has no description - agents cannot reason about its purpose, and static analysis coverage is limited

    get-network-volume

    Tool 'create-network-volume' has no description - agents cannot reason about its purpose, and static analysis coverage is limited

    create-network-volume

    Tool 'update-network-volume' has no description - agents cannot reason about its purpose, and static analysis coverage is limited

    update-network-volume

    Tool 'delete-network-volume' has no description - agents cannot reason about its purpose, and static analysis coverage is limited

    delete-network-volume

    Tool 'list-container-registry-auths' has no description - agents cannot reason about its purpose, and static analysis coverage is limited

    list-container-registry-auths

    Tool 'get-container-registry-auth' has no description - agents cannot reason about its purpose, and static analysis coverage is limited

    get-container-registry-auth

    Tool 'create-container-registry-auth' has no description - agents cannot reason about its purpose, and static analysis coverage is limited

    create-container-registry-auth

    Tool 'delete-container-registry-auth' has no description - agents cannot reason about its purpose, and static analysis coverage is limited

    delete-container-registry-auth

    Fix: Review and remediate the identified issue.

  • InfoAS-014

    ℹ️Dependency Inventory Unavailable ×26

    Tool did not expose metadata.dependencies or repo_url, so supply-chain coverage is limited.

    list-podsget-podcreate-podupdate-podstart-podstop-poddelete-podlist-endpointsget-endpointcreate-endpointupdate-endpointdelete-endpointlist-templatesget-templatecreate-templateupdate-templatedelete-templatelist-network-volumesget-network-volumecreate-network-volumeupdate-network-volumedelete-network-volumelist-container-registry-authsget-container-registry-authcreate-container-registry-authdelete-container-registry-auth

    Fix: Review and remediate the identified issue.

  • InfoAS-002

    ⚠️Excessive Permissions ×15

    declared capabilities: filesystem access, environment variables

    create-podupdate-podupdate-template

    declared capabilities: filesystem access

    delete-podcreate-endpointdelete-templatecreate-network-volumeupdate-network-volumedelete-network-volumecreate-container-registry-authdelete-container-registry-auth

    declared capabilities: network access

    get-endpoint

    declared capabilities: network access, filesystem access

    update-endpointdelete-endpoint

    declared capabilities: code/command execution, filesystem access, environment variables

    create-template

    Fix: Tool requests broad permissions (exec/fs/network). Validate input parameters using Enums where possible, and restrict file system operations to explicit allowed directories.

  • InfoAS-010

    🔑Insecure Secret Handling

    create-container-registry-auth:input parameter "password" accepts a credential (informational; not evidence of insecure handling)

    Fix: Avoid accepting raw credentials as input parameters. Use secret managers (e.g. 1Password CLI, AWS Secrets Manager) and ensure credentials are never logged or stored in agent traces.

Scan this tool yourself

Reproduce this audit locally, integrate into CI, or let your agent audit its own tools.

Install once, then scan any MCP server:

$ curl -sfL https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-scanner/main/install.sh | bash
$ tooltrust-scanner scan --server "npx -y runpod-runpod-mcp-ts"

Adjust the package name if your npm registry name differs from the tool ID. View source

Add badge to your README

Copy this Markdown to show your ToolTrust grade on GitHub.

[![ToolTrust Grade A](https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-directory/main/docs/badges/grade-a.svg)](https://github.com/AgentSafe-AI/tooltrust-directory)