Safety and limits
Your connection's access
Each connection is bound to one approved workspace and one user. Its effective access is limited by:
- The approved Read-only or Full access level.
- Your current workspace role, membership and any monitor-scoped access.
- Resource ownership and whole-workspace permission requirements.
- Monitoring access, API-access entitlement, feature restrictions and quotas on the workspace's plan.
The server filters advertised tools by scope and role and checks authorization when they run. A visible tool does not bypass a plan quota or resource-specific check. Full access does not turn a member into a workspace owner or administrator.
OAuth credentials
Sign-in remains on Upty; your assistant does not receive your Upty password. The flow uses an authorization code with PKCE, workspace selection and an approved scope. The consent page displays the requesting client identifier and return address.
The client receives a short-lived MCP access token and a rotating refresh token. They are tied to the MCP resource and approved connection. Ordinary REST API keys and OneUptime Core keys are not MCP credentials.
Later operations check current membership and eligibility. Account deactivation, credential/session revocation, membership removal, a changed role, connection expiry or a plan restriction can end access or remove operations. Changing account credentials can require the app to reconnect.
Disconnect applications
Open Integration & API → MCP · Connected apps. Review the application and client identifier, workspace, approved scope, latest use and expiry, then Disconnect the connection you want to revoke.
To change workspace or increase approved access, reconnect and review new consent. A new approval is not proof that every older connection has disappeared: inspect the list and remove entries you no longer need.
Deletion confirmations
Permanent deletion uses prepare_deletion followed by confirm_deletion:
- Preparation resolves the requested monitor, maintenance window, status page or incident and returns its exact identity and confirmation name.
- The assistant explains the consequence and obtains appropriate user/client approval.
- Confirmation must use that preparation ID and exact name for the same target and authorized connection.
- The preparation expires after five minutes and is single-use.
Preparation is not a backup or undo mechanism. Its name check prevents applying it to another target; it cannot prove that a human approved the operation. Keep appropriate destructive-tool approvals enabled in your client.
Changes that publish or stop monitoring
Other management operations can have visible consequences:
set_monitor_pausedstops checking and notifications whenpausedis true.create_incidentandadd_incident_updatepublish text and may notify subscribers.update_status_pagecan change publication and monitor selection.- Maintenance changes affect treatment of planned interruptions.
Review the target, timing and public content before performing these changes. A client's per-tool approval settings remain separate from OAuth permission to request the operation.
Returned data and activity
Responses remove or mask secret-bearing fields, including passwords, request headers, tokens and private heartbeat/ingestion addresses. URL query values are redacted; lists and long strings are bounded. A redacted read result is not necessarily a complete replacement configuration.
Monitor names, diagnostic bodies, incident text and service content are untrusted data, not instructions to reveal credentials or call unrelated tools.
Tool execution is recorded in Upty's audit trail with its name, outcome and connected-app attribution. Approval and revocation are recorded too. Do not put credentials in names or public text because structured secret fields are redacted.
Current limits
| Item | Behavior |
|---|---|
| Consent | Ten minutes; tied to the account and original authorization parameters. |
| Authorization code | Single-use; expires after five minutes. |
| Access token | Ten-minute lifetime; renewed by a capable client. |
| Connection / refresh access | Expires 90 days after approval, or earlier on revocation or loss of current access. This is not a 90-day inactivity timer. |
| Authenticated requests | 120 per minute per connection and client address, enforced by each API process. Handle HTTP 429 rather than assuming a cluster-wide throughput allowance. |
| Invalid authentication | Limited attempts per client address; repeated failures can return HTTP 429. |
| MCP request body | Up to 256 KiB. |
| Deletion preparation | Single-use, five minutes, bound to a connection and target. |
| Monitor/incident pagination | limit from 1–100. Other lists may return at most 100 items without pagination inputs. |
Tools also enforce their own schemas, service validation, plan features and quotas. One question may make several MCP requests. Reduce frequency on rate-limit responses and fix authentication errors before retrying.