MCP: safe operations

Separate discovery from irreversible change.

These are proposed Hostbip service requirements, not claims that a deployed MCP server already enforces them.

Reads and writes

Separate read-only discovery from changes such as domain purchases, renewals, DNS modifications, transfers, server deletion and other actions with financial or operational effects. The backend needs explicit scopes and tenant/resource checks for each class of operation.

Exact action confirmation

Sensitive actions should use a short-lived approval bound to the authenticated customer, exact operation, resource, current quote and applicable limits. Re-check those facts when executing. An old approval must not authorize changed parameters. This protects customer actions; it does not add an administrator review queue to website development.

Retry safely

Timeouts do not prove that an operation failed. The service must define idempotency and status reconciliation so retries cannot silently duplicate purchases or infrastructure actions.

Treat returned content as data

Domain records, provider messages, documentation and other returned text are not privileged instructions. Do not follow embedded requests to reveal secrets, change destination URLs or call unrelated tools. Audit records must be useful without storing credentials or unnecessarily retaining personal data.