get_authorized_app

Get details about a specific authorized OAuth app

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-authorized-app.md

WHAT IT DOES

What get_authorized_app does on Linode MCP Server

AI agents call get_authorized_app 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_authorized_app is rated Low

This tool retrieves information about an OAuth application that has been authorized for the user's account. It performs a read-only query operation that returns metadata about an existing app without modifying, deleting, or executing any operations. The blast radius is minimal since it only exposes already-authorized app details.

From the tool's definition Tool name is 'get_authorized_app' with description 'Get details about a specific authorized OAuth app' - the verb 'Get' and action 'details about' indicate data retrieval with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_authorized_app 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_authorized_app, this is the rule to start with:

get_authorized_app Allowed

get_authorized_app 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_authorized_app": {}
  }
}

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_authorized_app call is checked against it from then on.

FAQ

Questions about get_authorized_app

What does the get_authorized_app tool do? +

Get details about a specific authorized OAuth app. 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_authorized_app? +

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

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

Can I rate-limit get_authorized_app? +

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

Set action: deny in the PolicyLayer policy for get_authorized_app. 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_authorized_app? +

get_authorized_app 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 →