connections_revoke
Run connections.revoke through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/connections-revoke.md
What connections_revoke does on Appaloft
AI agents call connections_revoke to permanently remove resources in Appaloft, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
connectionId | string | Yes |
Parameters from the server's own tool schema.
Why connections_revoke is rated Critical
Revoking a connection permanently removes access or invalidates credentials/tokens associated with that connection. This is an irreversible action — once revoked, the connection cannot be restored without re-establishing it.
From the tool's definition 'connections_revoke' — 'revoke' indicates permanently terminating or invalidating a connection, which is typically irreversible. Sibling tools like 'account_sessions_revoke' confirm this server uses 'revoke' for irreversible invalidation actions.
Attacks that exploit this kind of access
The rule that runs connections_revoke safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Appaloft, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For connections_revoke, this is the rule to start with:
connections_revoke is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Appaloft, apply this rule, and every connections_revoke call is checked against it from then on.
Questions about connections_revoke
Run connections.revoke through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Destructive tool in the Appaloft MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
connections_revoke accepts 1 parameter: connectionId. Required: connectionId. The full parameter table on this page comes from the server's own tool schema.
Register the Appaloft MCP server in PolicyLayer and add a rule for connections_revoke: 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 Appaloft. Nothing to install.
connections_revoke is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the connections_revoke 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 connections_revoke. 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.
connections_revoke is provided by the Appaloft MCP server (@appaloft/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Appaloft, and thousands of servers like it.
Across the catalogue