# fix_bug

让 QA 专家修复 Bug

Agent View of the PolicyLayer registry record for `fix_bug`. HTML page: https://policylayer.com/tools/7836246-claude-team-mcp/fix-bug

## Facts

- Tool: `fix_bug`
- Server: Claude Team MCP (`7836246/claude-team-mcp`) — https://policylayer.com/tools/7836246-claude-team-mcp.md
- Homepage: https://github.com/7836246/claude-team-mcp
- 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": "fix_bug",
    "arguments": {}
  }
}
```

## Why fix_bug is rated High

A bug-fix tool that invokes an AI QA expert to fix bugs will likely write or modify code, and may execute code to verify the fix. The most severe applicable category is Execute, as it triggers external AI operations and likely modifies source files. Severity is high because automated code changes by an AI agent can introduce new bugs, security vulnerabilities, or unintended behavior.

From the tool's own definition: "fix_bug - 'QA 专家修复 Bug' (QA expert fixes bugs), implying automated code modification/execution"

## Use case

AI agents invoke fix_bug to trigger actions in Claude Team MCP. 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 Claude Team MCP:

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

## Other tools on Claude Team MCP (17)

- `run_workflow` — Execute — https://policylayer.com/tools/7836246-claude-team-mcp/run-workflow.md
- `team_work` — Execute — https://policylayer.com/tools/7836246-claude-team-mcp/team-work.md
- `analyze_project_structure` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/analyze-project-structure.md
- `ask_expert` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/ask-expert.md
- `code_review` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/code-review.md
- `cost_estimate` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/cost-estimate.md
- `explain_plan` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/explain-plan.md
- `history_context` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/history-context.md
- `history_get` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/history-get.md
- `history_list` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/history-list.md
- `history_search` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/history-search.md
- `list_workflows` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/list-workflows.md
- `read_project_files` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/read-project-files.md
- `suggest_workflow` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/suggest-workflow.md
- `team_dashboard` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/team-dashboard.md
- `usage_stats` — Read — https://policylayer.com/tools/7836246-claude-team-mcp/usage-stats.md
- `generate_commit_message` — Write — https://policylayer.com/tools/7836246-claude-team-mcp/generate-commit-message.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=7836246-claude-team-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/7836246-claude-team-mcp