delete_oauth_credential
Permanently delete an OAuth credential. Fails with a list of referencing actions if any still use it — reassign or remove those actions first.
This record as markdown: /tools/deloc-mcp/delete-oauth-credential.md
What delete_oauth_credential does on Deloc
AI agents call delete_oauth_credential to permanently remove resources in Deloc, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_oauth_credential is rated Critical
This tool irreversibly destroys OAuth credential data. Although it includes a safety check (failing if actions still reference it), the core operation is destructive deletion that cannot be undone. The blast radius is high: a misused deletion could break authentication for dependent services or applications, requiring manual credential recreation and reassignment.
From the tool's definition Tool performs a 'Permanently delete' action on OAuth credentials — the description explicitly states the deletion is permanent and irreversible.
Attacks that exploit this kind of access
The rule that runs delete_oauth_credential safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Deloc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_oauth_credential, this is the rule to start with:
delete_oauth_credential 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 Deloc, apply this rule, and every delete_oauth_credential call is checked against it from then on.
Questions about delete_oauth_credential
Permanently delete an OAuth credential. Fails with a list of referencing actions if any still use it — reassign or remove those actions first. It is categorised as a Destructive tool in the Deloc MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Deloc MCP server in PolicyLayer and add a rule for delete_oauth_credential: 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 Deloc. Nothing to install.
delete_oauth_credential 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 delete_oauth_credential 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 delete_oauth_credential. 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.
delete_oauth_credential is provided by the Deloc MCP server (delocdev/deloc-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Deloc, and thousands of servers like it.
Across the catalogue