Manage tunnel lifecycle and renewal
The agent maintains the operational state of leased IPs by renewing subscriptions before expiration, revoking unused tunnels to free up allowances, and updating DNS records as needed.
How it works
The agent uses lease_status to monitor expiry and current usage. It calls renew_lease to invoice another term for the plan. If a tunnel is no longer needed, it calls revoke_tunnel to retire the peer and return the slot to the plan's allowance. It can also use set_reverse_dns to update PTR records or set_autorenew to manage subscription billing cycles. The agent must check the access_token for each operation.
Prompt
Paste this into an agent that has the servers below connected. Adjust the names and dates to your own.
Check the status of the lease with token 'abc123', renew the lease for the current plan, and revoke the tunnel with ID 'tunnel-456'.MCP servers it needs
Source
The vendor page this playbook is drawn from, and the passage that supports it.
An agent that provisions a peer per short-lived worker and never revokes one exhausts the plan's allowance and then cannot bring the next machine up.MCP — let an assistant order and provision a static IP for you | AnchoredIP