# close

Cierra el browser. Útil para liberar memoria entre runs largos.

Agent View of the PolicyLayer registry record for `close`. HTML page: https://policylayer.com/tools/4bis-relay-showcase/close

## Facts

- Tool: `close`
- Server: 4bis Relay Showcase (`FourBis/4bis.relay-showcase`) — https://policylayer.com/tools/4bis-relay-showcase.md
- Homepage: https://github.com/FourBis/4bis.relay-showcase
- Risk category: Execute (High risk)
- Registry record: grade D, identity unverified
- 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": "close",
    "arguments": {}
  }
}
```

## Why close is rated High

Closes the browser process, triggering an external operation that terminates a running resource.

From the tool's own definition: "Cierra el browser. Útil para liberar memoria"

## Use case

AI agents invoke close to trigger actions in 4bis Relay Showcase. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "close": {
      "limits": [
        {
          "counter": "close_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on 4bis Relay Showcase (15)

- `navigate` — Execute — https://policylayer.com/tools/4bis-relay-showcase/navigate.md
- `get_html` — Read — https://policylayer.com/tools/4bis-relay-showcase/get-html.md
- `get_issue` — Read — https://policylayer.com/tools/4bis-relay-showcase/get-issue.md
- `get_pull` — Read — https://policylayer.com/tools/4bis-relay-showcase/get-pull.md
- `get_repo` — Read — https://policylayer.com/tools/4bis-relay-showcase/get-repo.md
- `get_text` — Read — https://policylayer.com/tools/4bis-relay-showcase/get-text.md
- `get_title` — Read — https://policylayer.com/tools/4bis-relay-showcase/get-title.md
- `get_url` — Read — https://policylayer.com/tools/4bis-relay-showcase/get-url.md
- `list_commits` — Read — https://policylayer.com/tools/4bis-relay-showcase/list-commits.md
- `list_issues` — Read — https://policylayer.com/tools/4bis-relay-showcase/list-issues.md
- `list_pulls` — Read — https://policylayer.com/tools/4bis-relay-showcase/list-pulls.md
- `screenshot` — Read — https://policylayer.com/tools/4bis-relay-showcase/screenshot.md
- `search_issues` — Read — https://policylayer.com/tools/4bis-relay-showcase/search-issues.md
- `comment_issue` — Write — https://policylayer.com/tools/4bis-relay-showcase/comment-issue.md
- `create_issue` — Write — https://policylayer.com/tools/4bis-relay-showcase/create-issue.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=4bis-relay-showcase · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/4bis-relay-showcase