disconnect_service
Disconnect a connected service. Removes stored credentials.
This record as markdown: /tools/io-github-0nork-0nmcp/disconnect-service.md
What disconnect_service does on 0nmcp
AI agents use disconnect_service to create or update resources in 0nmcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 0nmcp environment.
Why disconnect_service is rated Medium
Removing credentials is a reversible data modification (Write category) rather than permanent deletion. The blast radius is medium: disconnecting a service could disrupt workflows, but credentials can be re-added. Not Execute (no command/code execution), not Destructive (not irreversible), not Financial.
From the tool's definition Tool description states 'Disconnect a connected service. Removes stored credentials.' The action modifies stored state (credentials removal) reversibly—reconnection is possible.
Attacks that exploit this kind of access
The rule that runs disconnect_service safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 0nmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For disconnect_service, this is the rule to start with:
disconnect_service stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 0nmcp, apply this rule, and every disconnect_service call is checked against it from then on.
Questions about disconnect_service
Disconnect a connected service. Removes stored credentials. It is categorised as a Write tool in the 0nmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 0n MCP server in PolicyLayer and add a rule for disconnect_service: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches 0nmcp. Nothing to install.
disconnect_service is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the disconnect_service rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for disconnect_service. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
disconnect_service is provided by the 0n MCP server (0nmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 0n, and thousands of servers like it.
This server
Across the catalogue