create_instance_disk
Create a new disk for a Linode instance
This record as markdown: /tools/takashito-linode-mcp-server/create-instance-disk.md
What create_instance_disk does on Linode MCP Server
AI agents use create_instance_disk 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_instance_disk is rated Medium
This tool creates new disk resources within a Linode instance, which is a reversible Write operation (disks can be deleted). However, it carries high severity because creating storage resources can consume paid cloud resources, impact billing, and affect instance capacity and performance.
From the tool's definition Tool name 'create_instance_disk' and description 'Create a new disk for a Linode instance' explicitly indicates creation of cloud infrastructure resources.
Attacks that exploit this kind of access
The rule that runs create_instance_disk 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 create_instance_disk, this is the rule to start with:
create_instance_disk stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Linode MCP Server, apply this rule, and every create_instance_disk call is checked against it from then on.
Questions about create_instance_disk
Create a new disk for a Linode instance. 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.
Register the Linode MCP Server MCP server in PolicyLayer and add a rule for create_instance_disk: 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.
create_instance_disk is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_instance_disk 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 create_instance_disk. 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.
create_instance_disk 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.
This server
Across the catalogue