What an assistant can and cannot do
An assistant connected to InfraNest sees only what you could see yourself, narrowed to the organization and scopes you gave it, and it can never change anything. Every request it makes shows up in the audit log under the token's or the app's name.
What it can do
- Read what the MCP server's tools cover: status, servers, monitors, incidents, DNS, domains, certificates, maintenance, the audit log and the uptime report — plus any other read in the API reference through
read_api. - Only in the organization you picked (Connect with InfraNest), or the organizations the token reaches.
- Only with your role's permissions, and only the scopes the token or connection holds.
What it will not do
- Change anything. Every tool is a read. An assistant that wants to change something has to tell you, and you, or a script you run, make the change.
- Read more than it may. Scopes, the organization, your organization's IP allowlist and the rate limits apply exactly as they do to a script. An IP allowlist checks the address of the computer running the assistant — or, for a hosted assistant such as claude.ai or ChatGPT, the provider's.
- Hand out secrets. Domain transfer codes, certificate files, agent and deploy tokens, status page subscriber lists and data exports are never returned through MCP, even when the token may read them directly.
- Follow instructions hidden in your data. A record value or an incident note can contain text written by someone else. InfraNest tells the assistant to treat it as data; it is still worth reading what an assistant proposes before you act on it.
Remove an assistant
- Connected with InfraNest (claude.ai, ChatGPT): open My account → Authorized apps and select Remove. It loses access at once. Removing the connector inside Claude or ChatGPT stops it there; remove it in InfraNest too, so its access ends on our side as well.
- With a token (Claude Code, Cursor, VS Code, Claude Desktop): revoke the token under My account → Developer. Every tool call with it fails from then on.
An organization's owners can see each token's and each authorized app's requests in the audit log.