list_resource_locks

List resource locks on the account

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/list-resource-locks.md

WHAT IT DOES

What list_resource_locks does on Linode MCP Server

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

This tool retrieves and displays existing resource locks for informational purposes. It has no side effects, does not modify state, and does not execute operations or delete data. It is purely a read operation for auditing or monitoring resource lock status.

From the tool's definition Tool name 'list_resource_locks' and description 'List resource locks on the account' indicate a retrieval/query operation that reads lock metadata without modifying, deleting, or executing operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_resource_locks Allowed

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

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

FAQ

Questions about list_resource_locks

What does the list_resource_locks tool do? +

List resource locks on the account. 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 list_resource_locks? +

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

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

Can I rate-limit list_resource_locks? +

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

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

list_resource_locks 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

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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