# team_dashboard

查看团队当前状态：可用专家、模型配置、最近活动

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

## Facts

- Tool: `team_dashboard`
- 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: Read (Low risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

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

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

## Why team_dashboard is rated Low

This tool retrieves and displays information about team state, expert availability, and activity history. It has no side effects, does not execute code, does not modify data, and does not commit financial transactions. It is purely informational/observational in nature, fitting the Read category with low severity since misuse would only expose visibility into system status.

From the tool's own definition: "Tool name 'team_dashboard' and description indicate viewing/monitoring only: '查看团队当前状态' (view team current status), 'available experts', 'model configuration', 'recent activity' — all read-only operations with no modification, deletion, or execution…"

## Use case

AI agents call team_dashboard to retrieve information from Claude Team MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "team_dashboard": {}
  }
}
```

## Other tools on Claude Team MCP (17)

- `fix_bug` — Execute — https://policylayer.com/tools/7836246-claude-team-mcp/fix-bug.md
- `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
- `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