New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

create_resource_lock

Create a resource lock

SERVERLinode MCP Server SOURCEtakashito/linode-mcp-server
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/takashito-linode-mcp-server/create-resource-lock.md

What create_resource_lock does on Linode MCP Server

AI agents use create_resource_lock to create or update resources in Linode MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Linode MCP Server environment.

Why create_resource_lock is rated Medium

Resource locks are reversible configuration changes—they can be created and removed. This is a Write operation rather than Execute because it doesn't run arbitrary code or commands; it simply creates a lock artifact. It's not Destructive because locks are not permanent state changes and can be undone.

From the tool's definition The tool name 'create_resource_lock' and description 'Create a resource lock' indicate creation of a lock resource.

Questions about create_resource_lock

What does the create_resource_lock tool do? +

Create a resource lock. It is categorised as a Write tool in the Linode MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_resource_lock? +

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

create_resource_lock is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_resource_lock? +

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

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Linode MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.