get_oauth_client

Get an OAuth client

SERVERLinode MCP Server SOURCEtakashito/linode-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/takashito-linode-mcp-server/get-oauth-client.md

WHAT IT DOES

What get_oauth_client does on Linode MCP Server

AI agents call get_oauth_client to retrieve information from Linode MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_oauth_client is rated Low

This tool retrieves existing OAuth client information from Linode's systems. It performs a data retrieval action typical of Read operations. While OAuth credentials are sensitive, the tool only fetches existing client data rather than creating, executing code, deleting, or performing financial operations.

From the tool's definition Tool name is 'get_oauth_client' and description states 'Get an OAuth client', indicating a retrieval/query operation without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_oauth_client safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Linode MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_oauth_client, this is the rule to start with:

get_oauth_client Allowed

get_oauth_client is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_oauth_client": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Linode MCP Server, apply this rule, and every get_oauth_client call is checked against it from then on.

FAQ

Questions about get_oauth_client

What does the get_oauth_client tool do? +

Get an OAuth client. It is categorised as a Read tool in the Linode MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_oauth_client? +

Register the Linode MCP Server MCP server in PolicyLayer and add a rule for get_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 get_oauth_client? +

get_oauth_client is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_oauth_client? +

Yes. Add a rate_limit block to the get_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 get_oauth_client completely? +

Set action: deny in the PolicyLayer policy for get_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 get_oauth_client? +

get_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.

KEEP EXPLORING

More on Linode MCP Server, and thousands of servers like it.

This server

All 416 Linode MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →