ToolTrust
A2/100
googleapis

mcp-toolbox

mcp1.4.0

@googleapis

MCP Toolbox for Databases is an open source MCP server for databases.

By googleapis | 56 findings | Scanned 6/16/2026 | tooltrust-scanner/v0.3.17 | 15.6k

5 Low51 Info

Risk Summary

Safe With Normal Controls

Secret Handling is the main signal, but overall risk remains within an acceptable range.

Potential impact: Sensitive credentials may be read, logged, or leaked to external systems.

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 (56)

  • LowAS-011

    ℹ️Missing Rate-Limit / Timeout ×5

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

    confirm_termshcs_queryhcs_write_recordcontract_readcontract_call

    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-014

    ℹ️Dependency Inventory Unavailable ×20

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

    get_termsconfirm_termsaccount_infohcs_monitorhcs_queryhcs_understandhcs_write_recordhcs_verify_recordhcs_audit_trailgovernance_monitorgovernance_analyzetoken_pricetoken_analyzetoken_monitoridentity_resolveidentity_verify_kycidentity_check_sanctionscontract_readcontract_callcontract_analyze

    Fix: Review and remediate the identified issue.

  • InfoAS-002

    ⚠️Excessive Permissions ×6

    declared capabilities: code/command execution

    confirm_termscontract_readcontract_call

    declared capabilities: network access, database access

    hcs_query

    declared capabilities: filesystem access, HTTP requests

    hcs_write_record

    declared capabilities: filesystem access

    identity_resolve

    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 ×25

    input parameter "api_key" accepts a credential (informational; not evidence of insecure handling)

    confirm_termsaccount_infohcs_monitorhcs_queryhcs_understandhcs_write_recordhcs_verify_recordhcs_audit_trailgovernance_monitorgovernance_analyzetoken_pricetoken_analyzetoken_monitoridentity_resolveidentity_verify_kycidentity_check_sanctionscontract_readcontract_callcontract_analyze

    input parameter "token_id" accepts a credential (informational; not evidence of insecure handling)

    governance_monitorgovernance_analyzetoken_pricetoken_analyzetoken_monitoridentity_verify_kyc

    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 mcp-toolbox"

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)