# seller_setup

The seller setup wizard. Returns wizard_url: a one-time signed-in link to the full browser wizard — it can GENERATE a payout wallet safely (keys shown once in the browser, never stored, user must confirm saving them), connect GitHub, and list the first repo. Call this when the user wants to start selling, has no wallet, or asks to finish setup; offer wizard_url.

Agent View of the PolicyLayer registry record for `seller_setup`. HTML page: https://policylayer.com/tools/com-gitbuyer-mcp/seller-setup

## Facts

- Tool: `seller_setup`
- Server: Mcp (`https://gitbuyer.com/mcp`) — https://policylayer.com/tools/com-gitbuyer-mcp.md
- Homepage: https://github.com/bitfent/gitbuyer
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "seller_setup",
    "arguments": {}
  }
}
```

## Why seller_setup is rated Medium

An AI agent can call seller_setup faster than any human can review: one bad instruction and it creates or modifies resources in Mcp by the hundred, each call as confident as the last.

## Use case

AI agents use seller_setup to create or update resources in Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp environment.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mcp:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "seller_setup": {
      "limits": [
        {
          "counter": "seller_setup_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Mcp (15)

- `delete_store` — Destructive — https://policylayer.com/tools/com-gitbuyer-mcp/delete-store.md
- `find_base` — Read — https://policylayer.com/tools/com-gitbuyer-mcp/find-base.md
- `get_github` — Read — https://policylayer.com/tools/com-gitbuyer-mcp/get-github.md
- `get_repo` — Read — https://policylayer.com/tools/com-gitbuyer-mcp/get-repo.md
- `get_sales` — Read — https://policylayer.com/tools/com-gitbuyer-mcp/get-sales.md
- `get_stats` — Read — https://policylayer.com/tools/com-gitbuyer-mcp/get-stats.md
- `get_store` — Read — https://policylayer.com/tools/com-gitbuyer-mcp/get-store.md
- `get_traffic` — Read — https://policylayer.com/tools/com-gitbuyer-mcp/get-traffic.md
- `list_stores` — Read — https://policylayer.com/tools/com-gitbuyer-mcp/list-stores.md
- `search_repos` — Read — https://policylayer.com/tools/com-gitbuyer-mcp/search-repos.md
- `whoami` — Read — https://policylayer.com/tools/com-gitbuyer-mcp/whoami.md
- `create_payout_wallet` — Write — https://policylayer.com/tools/com-gitbuyer-mcp/create-payout-wallet.md
- `create_store` — Write — https://policylayer.com/tools/com-gitbuyer-mcp/create-store.md
- `set_payout_wallets` — Write — https://policylayer.com/tools/com-gitbuyer-mcp/set-payout-wallets.md
- `update_store` — Write — https://policylayer.com/tools/com-gitbuyer-mcp/update-store.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-gitbuyer-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-gitbuyer-mcp