# delete_store

Take a store down and void its checkout so old links stop being payable.

Agent View of the PolicyLayer registry record for `delete_store`. HTML page: https://policylayer.com/tools/com-gitbuyer-mcp/delete-store

## Facts

- Tool: `delete_store`
- Server: Mcp (`https://gitbuyer.com/mcp`) — https://policylayer.com/tools/com-gitbuyer-mcp.md
- Homepage: https://github.com/bitfent/gitbuyer
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 2 (2 required)
- Recommended policy verdict: Hidden

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `repo` | string | yes |  |
| `owner` | string | yes |  |

Parameters from the server's own tool schema.

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "delete_store",
    "arguments": {
      "repo": "<repo>",
      "owner": "<owner>"
    }
  }
}
```

## Why delete_store is rated Critical

An AI agent that decides to call delete_store doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Mcp is gone. There is no undo for destructive operations.

## Use case

AI agents call delete_store to permanently remove resources in Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_store"
  ]
}
```

## Other tools on Mcp (15)

- `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
- `seller_setup` — Write — https://policylayer.com/tools/com-gitbuyer-mcp/seller-setup.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