Execute approved physical access runbook
A human operator performs a physical action such as a power cycle or cable check based on an approved runbook, returning status updates and evidence while keeping private keys secure.
How it works
The agent prepares a brief for a physical access task, including an approved runbook (e.g., power cycle, cable check), the authorized contact, stop conditions, and escalation path. It explicitly excludes passwords and private keys. The agent submits the task via the MCP server, waits for the operator's confirmation of feasibility, and tracks the execution status and evidence delivery through the API.
Prompt
Paste this into an agent that has the servers below connected. Adjust the names and dates to your own.
Provide an approved runbook for a power cycle and cable check at [Location]. Name the authorized contact, stop conditions, and escalation path. Keep passwords and private keys out of the brief. Submit the task for execution.MCP servers it needs
Source
The vendor page this playbook is drawn from, and the passage that supports it.
Provide an approved runbook for a power cycle, cable check, device label or rack visit. Name the authorized contact, stop conditions and escalation path.Start here: human field work through MCP or REST | Agent Groundcrew