AI agents call list_resource_locks to retrieve information from Linode MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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.
Documented attack patterns abuse exactly the kind of access list_resource_locks gives an agent:
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 list_resource_locks:
{
"version": "1",
"default": "deny",
"tools": {
"list_resource_locks": {}
}
}list_resource_locks is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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.
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.
list_resource_locks is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
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.
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.