# retry_sites

Re-run generation for FAILED sites in a project (the MCP equivalent of the dashboard Retry button). Pass onlyFailed: true to retry every failed/cancelled site, or siteIds: [...] to retry specific ones. Only sites in a failed/cancelled state are retried; others are reported under skipped. Use list_sites first to see statuses.

Agent View of the PolicyLayer registry record for `retry_sites`. HTML page: https://policylayer.com/tools/a3plus-mcp/retry-sites

## Facts

- Tool: `retry_sites`
- Server: A3plus (`a3plus-mcp`) — https://policylayer.com/tools/a3plus-mcp.md
- Install: `npx -y a3plus-mcp`
- Homepage: https://www.npmjs.com/package/a3plus-mcp
- Risk category: Execute (High risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 3 (1 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `siteIds` | array | no | Specific site IDs to retry (alternative to onlyFailed). |
| `projectId` | string | yes | The A3Plus project ID. |
| `onlyFailed` | boolean | no | Retry ALL failed/cancelled sites in the project. |

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": "retry_sites",
    "arguments": {
      "projectId": "<projectId>"
    }
  }
}
```

## Why retry_sites is rated High

retry_sites triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Risk signals: Bulk/mass operation — affects multiple targets

## Use case

AI agents invoke retry_sites to trigger actions in A3plus. 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 A3plus:

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

## Other tools on A3plus (60)

- `delete_article` — Destructive — https://policylayer.com/tools/a3plus-mcp/delete-article.md
- `delete_sites` — Destructive — https://policylayer.com/tools/a3plus-mcp/delete-sites.md
- `list_domains` — Destructive — https://policylayer.com/tools/a3plus-mcp/list-domains.md
- `remove_project_member` — Destructive — https://policylayer.com/tools/a3plus-mcp/remove-project-member.md
- `update_article` — Destructive — https://policylayer.com/tools/a3plus-mcp/update-article.md
- `transfer_sites` — Financial — https://policylayer.com/tools/a3plus-mcp/transfer-sites.md
- `audit_project_articles` — Read — https://policylayer.com/tools/a3plus-mcp/audit-project-articles.md
- `bind_domain` — Read — https://policylayer.com/tools/a3plus-mcp/bind-domain.md
- `bredgio_list_agents` — Read — https://policylayer.com/tools/a3plus-mcp/bredgio-list-agents.md
- `bredgio_logout` — Read — https://policylayer.com/tools/a3plus-mcp/bredgio-logout.md
- `bredgio_status` — Read — https://policylayer.com/tools/a3plus-mcp/bredgio-status.md
- `bredgio_task_status` — Read — https://policylayer.com/tools/a3plus-mcp/bredgio-task-status.md
- `get_article` — Read — https://policylayer.com/tools/a3plus-mcp/get-article.md
- `get_intake_schema` — Read — https://policylayer.com/tools/a3plus-mcp/get-intake-schema.md
- `get_pack` — Read — https://policylayer.com/tools/a3plus-mcp/get-pack.md
- `get_playbook` — Read — https://policylayer.com/tools/a3plus-mcp/get-playbook.md
- `get_project` — Read — https://policylayer.com/tools/a3plus-mcp/get-project.md
- `get_project_readiness` — Read — https://policylayer.com/tools/a3plus-mcp/get-project-readiness.md
- `get_site_brand` — Read — https://policylayer.com/tools/a3plus-mcp/get-site-brand.md
- `get_site_content` — Read — https://policylayer.com/tools/a3plus-mcp/get-site-content.md
- `get_site_faq` — Read — https://policylayer.com/tools/a3plus-mcp/get-site-faq.md
- `get_site_seo` — Read — https://policylayer.com/tools/a3plus-mcp/get-site-seo.md
- `get_static_pages` — Read — https://policylayer.com/tools/a3plus-mcp/get-static-pages.md
- `gsc_search_analytics` — Read — https://policylayer.com/tools/a3plus-mcp/gsc-search-analytics.md
- `gsc_site_detail` — Read — https://policylayer.com/tools/a3plus-mcp/gsc-site-detail.md
- `gsc_sites` — Read — https://policylayer.com/tools/a3plus-mcp/gsc-sites.md
- `gsc_zero_data_sites` — Read — https://policylayer.com/tools/a3plus-mcp/gsc-zero-data-sites.md
- `index_coverage_report` — Read — https://policylayer.com/tools/a3plus-mcp/index-coverage-report.md
- `list_articles` — Read — https://policylayer.com/tools/a3plus-mcp/list-articles.md
- `list_pack_categories` — Read — https://policylayer.com/tools/a3plus-mcp/list-pack-categories.md
- …and 30 more: https://policylayer.com/tools/a3plus-mcp.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=a3plus-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/a3plus-mcp