# get_gpu_monitor_data

Get GPU monitor data (XPack)

Agent View of the PolicyLayer registry record for `get_gpu_monitor_data`. HTML page: https://policylayer.com/tools/eaveluo-1panel-mcp/get-gpu-monitor-data

## Facts

- Tool: `get_gpu_monitor_data`
- Server: 1Panel MCP Server (`eaveluo/1panel-mcp`) — https://policylayer.com/tools/eaveluo-1panel-mcp.md
- Homepage: https://github.com/EaveLuo/1panel-mcp
- Risk category: Read (Low risk)
- Registry record: grade F, 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": "get_gpu_monitor_data",
    "arguments": {}
  }
}
```

## Why get_gpu_monitor_data is rated Low

This tool retrieves GPU monitoring metrics and statistics without modifying system state, executing commands, or triggering external operations. While it accesses sensitive infrastructure data, its read-only nature and monitoring purpose place it in the Read category with low severity. An AI agent retrieving GPU metrics poses minimal risk compared to tools that modify or delete data.

From the tool's own definition: "Tool name 'get_gpu_monitor_data' and description 'Get GPU monitor data' indicate a retrieval operation with no modification or side effects. The 'Get' verb and monitoring context (reading metrics) confirm read-only access."

## Use case

AI agents call get_gpu_monitor_data to retrieve information from 1Panel MCP Server 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 1Panel MCP Server:

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

## Other tools on 1Panel MCP Server (285)

- `clean_compose_log` — Destructive — https://policylayer.com/tools/eaveluo-1panel-mcp/clean-compose-log.md
- `clean_container_log` — Destructive — https://policylayer.com/tools/eaveluo-1panel-mcp/clean-container-log.md
- `clean_monitor_data` — Destructive — https://policylayer.com/tools/eaveluo-1panel-mcp/clean-monitor-data.md
- `clear_recycle_bin` — Destructive — https://policylayer.com/tools/eaveluo-1panel-mcp/clear-recycle-bin.md
- `delete_ai_agent` — Destructive — https://policylayer.com/tools/eaveluo-1panel-mcp/delete-ai-agent.md
- `delete_ai_agent_account` — Destructive — https://policylayer.com/tools/eaveluo-1panel-mcp/delete-ai-agent-account.md
- `delete_backup` — Destructive — https://policylayer.com/tools/eaveluo-1panel-mcp/delete-backup.md
- `delete_backup_account` — Destructive — https://policylayer.com/tools/eaveluo-1panel-mcp/delete-backup-account.md
- `delete_certificate` — Destructive — https://policylayer.com/tools/eaveluo-1panel-mcp/delete-certificate.md
- `delete_clam_config` — Destructive — https://policylayer.com/tools/eaveluo-1panel-mcp/delete-clam-config.md
- `delete_cronjob` — Destructive — https://policylayer.com/tools/eaveluo-1panel-mcp/delete-cronjob.md
- `delete_database` — Destructive — https://policylayer.com/tools/eaveluo-1panel-mcp/delete-database.md
- `delete_file` — Destructive — https://policylayer.com/tools/eaveluo-1panel-mcp/delete-file.md
- `delete_firewall_rule` — Destructive — https://policylayer.com/tools/eaveluo-1panel-mcp/delete-firewall-rule.md
- `delete_ftp_user` — Destructive — https://policylayer.com/tools/eaveluo-1panel-mcp/delete-ftp-user.md
- `delete_host` — Destructive — https://policylayer.com/tools/eaveluo-1panel-mcp/delete-host.md
- `delete_host_group` — Destructive — https://policylayer.com/tools/eaveluo-1panel-mcp/delete-host-group.md
- `delete_host_ssh_key` — Destructive — https://policylayer.com/tools/eaveluo-1panel-mcp/delete-host-ssh-key.md
- `delete_mcp_server` — Destructive — https://policylayer.com/tools/eaveluo-1panel-mcp/delete-mcp-server.md
- `delete_ollama_model` — Destructive — https://policylayer.com/tools/eaveluo-1panel-mcp/delete-ollama-model.md
- `delete_snapshot` — Destructive — https://policylayer.com/tools/eaveluo-1panel-mcp/delete-snapshot.md
- `delete_website` — Destructive — https://policylayer.com/tools/eaveluo-1panel-mcp/delete-website.md
- `delete_website_domain` — Destructive — https://policylayer.com/tools/eaveluo-1panel-mcp/delete-website-domain.md
- `partition_disk` — Destructive — https://policylayer.com/tools/eaveluo-1panel-mcp/partition-disk.md
- `prune_containers` — Destructive — https://policylayer.com/tools/eaveluo-1panel-mcp/prune-containers.md
- `recover_snapshot` — Destructive — https://policylayer.com/tools/eaveluo-1panel-mcp/recover-snapshot.md
- `recreate_snapshot` — Destructive — https://policylayer.com/tools/eaveluo-1panel-mcp/recreate-snapshot.md
- `remove_compose` — Destructive — https://policylayer.com/tools/eaveluo-1panel-mcp/remove-compose.md
- `remove_container` — Destructive — https://policylayer.com/tools/eaveluo-1panel-mcp/remove-container.md
- `remove_image` — Destructive — https://policylayer.com/tools/eaveluo-1panel-mcp/remove-image.md
- …and 255 more: https://policylayer.com/tools/eaveluo-1panel-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=eaveluo-1panel-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/eaveluo-1panel-mcp