revoke_connection
Immediately revoke a DenkOps connection token by its connection_id.
This record as markdown: /tools/denkopsai-mcp/revoke-connection.md
What revoke_connection does on Denkopsai
AI agents call revoke_connection to permanently remove resources in Denkopsai, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
connection_id | string | Yes |
Parameters from the server's own tool schema.
Why revoke_connection is rated Critical
Revoking a connection token is an irreversible action — once revoked, the token is invalidated and cannot be restored. This disrupts active connections and access, making it destructive in nature. Misuse by an AI agent could immediately sever legitimate integrations or access pathways.
From the tool's definition "Immediately revoke a DenkOps connection token by its connection_id"
Attacks that exploit this kind of access
The rule that runs revoke_connection safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Denkopsai, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For revoke_connection, this is the rule to start with:
revoke_connection 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 Denkopsai, apply this rule, and every revoke_connection call is checked against it from then on.
Questions about revoke_connection
Immediately revoke a DenkOps connection token by its connection_id. It is categorised as a Destructive tool in the Denkopsai MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
revoke_connection accepts 1 parameter: connection_id. Required: connection_id. The full parameter table on this page comes from the server's own tool schema.
Register the Denkopsai MCP server in PolicyLayer and add a rule for revoke_connection: 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 Denkopsai. Nothing to install.
revoke_connection 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 revoke_connection 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 revoke_connection. 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.
revoke_connection is provided by the Denkopsai MCP server (@denkopsai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Denkopsai, and thousands of servers like it.
Across the catalogue