execute_command

3 registry entries were observed exposing a tool named execute_command — 3 of them as a privileged capability (a name matching exec / write / delete keywords).

Spelled execute_command, execute-command in the wild — all one tool for the purposes of this page.

Every row is point-in-time scan output, dated below. Forge has an observed tool surface for 12,346 of 40,589 scannable entries (30%) — an entry that has not been scanned cannot appear here, so absence from this list is not evidence that an entry does not expose this tool.

  1. io.github.ezrabrilliant/staruml-mcpMCPattestedtrust 85/100 · Aprivileged
    v0.2.0

    MCP server for StarUML — generate UML diagrams from AI agents via stdio or HTTP.

    ClaudeCursorCopilotGemini
    io.github.ezrabrilliantUnknown5mo agonpmGitHubobserved · static extraction
    mcp
  2. hyper-mcp-shellMCPcommunitytrust 60/100 · Bprivileged
    v1.1.2
    ↓ 91/wk

    A shell for the ModelContextProtocol

    ClaudeCursorCopilotGemini
    UnknownUnknown1y agonpmobserved · static extraction
  3. @guardbee/mcp-ai-code-scannerMCPcommunitytrust 60/100 · Bprivileged
    v0.3.2
    ↓ 69/wk
    ★ 1

    Scans code for insecure LLM/AI integration: exposed keys, unsafe output, prompt injection

    ClaudeCursorCopilotGemini
    io.github.4hmetuyarMIT14d agonpmGitHubobserved · static extraction
    mcp

All indexed toolsSearch the registry for execute_command