Critical Risk →

delete_oauth_client

Delete an OAuth client

How to control delete_oauth_client ↓

What delete_oauth_client does on Linode MCP Server

AI agents call delete_oauth_client to permanently remove resources in Linode MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete_oauth_client needs a policy

Deleting an OAuth client is an irreversible action that removes authentication credentials and access tokens. This prevents legitimate applications from authenticating and could disrupt services relying on that OAuth client. The action cannot be undone without manual recreation.

From the tool's definition Tool name explicitly states 'delete_oauth_client' and description confirms 'Delete an OAuth client'. The verb 'delete' indicates irreversible removal of a resource.

Documented attack patterns abuse exactly the kind of access delete_oauth_client gives an agent:

How to control delete_oauth_client

PolicyLayer is an MCP gateway — it sits between your AI agents and Linode MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_oauth_client:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_oauth_client"
  ]
}

delete_oauth_client disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Linode MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_oauth_client

What does the delete_oauth_client tool do? +

Delete an OAuth client. It is categorised as a Destructive tool in the Linode MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_oauth_client? +

Register the Linode MCP Server MCP server in PolicyLayer and add a rule for delete_oauth_client: 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 Linode MCP Server. Nothing to install.

What risk level is delete_oauth_client? +

delete_oauth_client is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_oauth_client? +

Yes. Add a rate_limit block to the delete_oauth_client 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.

How do I block delete_oauth_client completely? +

Set action: deny in the PolicyLayer policy for delete_oauth_client. 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.

What MCP server provides delete_oauth_client? +

delete_oauth_client is provided by the Linode MCP Server MCP server (takashito/linode-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Linode MCP Server tool call.

Start from Linode MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

416 Linode MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.