ToolTrust
B17/100
node9-ai

node9-proxy

mcp2.41.0

@node9-ai

Access control for AI agents. Set what Claude Code, Codex, Gemini, Cursor and any MCP server are allowed to do, review risky actions before they run, and keep every action on the record.

By node9-ai | 45 findings | Scanned 10/26/2026 | tooltrust-scanner/v0.3.20 | 219

Repository health

Popularity and maintenance signals alongside the security grade.

View repository
Stars

219

current snapshot

Forks

Not collected

GitHub metadata pending

Contributors

Not collected

GitHub metadata pending

Last commit

Not collected

GitHub metadata pending

Last release

Not collected

GitHub metadata pending

Release version

Not collected

Latest GitHub release

Stars trend

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

1d
2026-10-102026-10-10

Pull request activity

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

2026-08-242026-09-21

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

TypeScriptApache-2.0Developer Tools7.8k/mo npm downloadsLast scan Oct 26, 2026
1 High14 Low30 Info

Risk Summary

Safe With Normal Controls

Dep Visibility 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 (45)

  • HighAS-003

    🔀Scope Mismatch

    search_competitors:tool name "search_competitors" implies read-only operation but declares exec permission

    Fix: Ensure tool names, descriptions, and permission declarations are internally consistent. Use explicit naming conventions that fully reflect actual capabilities.

  • LowAS-002

    ⚠️Excessive Permissions ×2

    input schema exposes 16 properties (threshold: 10)

    get_meta_ads

    input schema exposes 14 properties (threshold: 10)

    search_meta_ads_by_keyword

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

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

    get_meta_adsanalyze_ad_imageanalyze_ad_videosearch_meta_ads_by_keywordshow_ad_carouselget_google_platform_idget_google_adsget_google_ad_detailssearch_linkedin_adssearch_competitorssearch_tiktok_adsget_tiktok_ad_details

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

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

    submit_feedbackget_credit_balanceget_meta_platform_idget_meta_adsanalyze_ad_imageanalyze_ad_videoget_competitive_briefsearch_meta_ads_by_keywordshow_ad_carouselget_google_platform_idget_google_adsget_google_ad_detailssearch_linkedin_adsget_linkedin_ad_detailssearch_competitorssearch_tiktok_adsget_tiktok_ad_details

    Fix: Review and remediate the identified issue.

  • InfoAS-002

    ⚠️Excessive Permissions ×12

    declared capabilities: network access, HTTP requests

    get_meta_adssearch_meta_ads_by_keywordget_google_adsget_google_ad_detailsget_tiktok_ad_details

    declared capabilities: network access

    analyze_ad_imageanalyze_ad_videoshow_ad_carouselget_google_platform_idsearch_linkedin_ads

    declared capabilities: code/command execution, network access, database access

    search_competitors

    declared capabilities: network access, database access, HTTP requests

    search_tiktok_ads

    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

    search_linkedin_ads:input parameter "pagination_token" 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 node9-proxy"

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 B](https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-directory/main/docs/badges/grade-b.svg)](https://github.com/AgentSafe-AI/tooltrust-directory)