get_resource_lock

What get_resource_lock does on Linode MCP Server

AI agents call get_resource_lock 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.

Why get_resource_lock is rated Low

This tool retrieves information about a resource lock status or metadata. It performs a query operation that does not create, modify, delete, or execute any changes to infrastructure. The read-only nature and lack of side effects place it in the Read category with low severity, as obtaining lock information poses minimal risk to system integrity.

From the tool's definition Tool name 'get_resource_lock' and description 'Get a specific resource lock' indicate a retrieval operation with no side effects. The verb 'Get' is a read operation that queries the state of an existing resource lock without modifying it.

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

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

Questions about get_resource_lock