# resize_volume

Resize a volume

Agent View of the PolicyLayer registry record for `resize_volume`. HTML page: https://policylayer.com/tools/takashito-linode-mcp-server/resize-volume

## Facts

- Tool: `resize_volume`
- Server: Linode MCP Server (`takashito/linode-mcp-server`) — https://policylayer.com/tools/takashito-linode-mcp-server.md
- Homepage: https://github.com/takashito/linode-mcp-server
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "resize_volume",
    "arguments": {}
  }
}
```

## Why resize_volume is rated Medium

Resizing a volume modifies data storage configuration reversibly (volumes can be resized up or down), making this a Write operation rather than Execute or Destructive. Severity is high because misconfiguration could cause service disruption, data unavailability, or unexpected costs if an AI agent resizes volumes without proper constraints. The action is reversible, preventing it from being Destructive.

From the tool's own definition: "Tool name 'resize_volume' indicates modification of cloud storage resource size; description 'Resize a volume' confirms it modifies an existing resource state."

## Use case

AI agents use resize_volume 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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Linode MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "resize_volume": {
      "limits": [
        {
          "counter": "resize_volume_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Linode MCP Server (415)

- `cancel_account` — Destructive — https://policylayer.com/tools/takashito-linode-mcp-server/cancel-account.md
- `cancel_backups` — Destructive — https://policylayer.com/tools/takashito-linode-mcp-server/cancel-backups.md
- `cancel_object_storage` — Destructive — https://policylayer.com/tools/takashito-linode-mcp-server/cancel-object-storage.md
- `delete_alert_definition` — Destructive — https://policylayer.com/tools/takashito-linode-mcp-server/delete-alert-definition.md
- `delete_api_token` — Destructive — https://policylayer.com/tools/takashito-linode-mcp-server/delete-api-token.md
- `delete_config_interface` — Destructive — https://policylayer.com/tools/takashito-linode-mcp-server/delete-config-interface.md
- `delete_domain` — Destructive — https://policylayer.com/tools/takashito-linode-mcp-server/delete-domain.md
- `delete_domain_record` — Destructive — https://policylayer.com/tools/takashito-linode-mcp-server/delete-domain-record.md
- `delete_firewall` — Destructive — https://policylayer.com/tools/takashito-linode-mcp-server/delete-firewall.md
- `delete_firewall_device` — Destructive — https://policylayer.com/tools/takashito-linode-mcp-server/delete-firewall-device.md
- `delete_image` — Destructive — https://policylayer.com/tools/takashito-linode-mcp-server/delete-image.md
- `delete_image_sharegroup` — Destructive — https://policylayer.com/tools/takashito-linode-mcp-server/delete-image-sharegroup.md
- `delete_instance` — Destructive — https://policylayer.com/tools/takashito-linode-mcp-server/delete-instance.md
- `delete_instance_config` — Destructive — https://policylayer.com/tools/takashito-linode-mcp-server/delete-instance-config.md
- `delete_instance_disk` — Destructive — https://policylayer.com/tools/takashito-linode-mcp-server/delete-instance-disk.md
- `delete_ipv4_address` — Destructive — https://policylayer.com/tools/takashito-linode-mcp-server/delete-ipv4-address.md
- `delete_ipv6_range` — Destructive — https://policylayer.com/tools/takashito-linode-mcp-server/delete-ipv6-range.md
- `delete_kubernetes_cluster` — Destructive — https://policylayer.com/tools/takashito-linode-mcp-server/delete-kubernetes-cluster.md
- `delete_kubernetes_control_plane_acl` — Destructive — https://policylayer.com/tools/takashito-linode-mcp-server/delete-kubernetes-control-plane-acl.md
- `delete_kubernetes_kubeconfig` — Destructive — https://policylayer.com/tools/takashito-linode-mcp-server/delete-kubernetes-kubeconfig.md
- `delete_kubernetes_node` — Destructive — https://policylayer.com/tools/takashito-linode-mcp-server/delete-kubernetes-node.md
- `delete_kubernetes_node_pool` — Destructive — https://policylayer.com/tools/takashito-linode-mcp-server/delete-kubernetes-node-pool.md
- `delete_kubernetes_service_token` — Destructive — https://policylayer.com/tools/takashito-linode-mcp-server/delete-kubernetes-service-token.md
- `delete_linode_interface` — Destructive — https://policylayer.com/tools/takashito-linode-mcp-server/delete-linode-interface.md
- `delete_log_destination` — Destructive — https://policylayer.com/tools/takashito-linode-mcp-server/delete-log-destination.md
- `delete_log_stream` — Destructive — https://policylayer.com/tools/takashito-linode-mcp-server/delete-log-stream.md
- `delete_longview_client` — Destructive — https://policylayer.com/tools/takashito-linode-mcp-server/delete-longview-client.md
- `delete_mysql_instance` — Destructive — https://policylayer.com/tools/takashito-linode-mcp-server/delete-mysql-instance.md
- `delete_nodebalancer` — Destructive — https://policylayer.com/tools/takashito-linode-mcp-server/delete-nodebalancer.md
- `delete_notification_channel` — Destructive — https://policylayer.com/tools/takashito-linode-mcp-server/delete-notification-channel.md
- …and 385 more: https://policylayer.com/tools/takashito-linode-mcp-server.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=takashito-linode-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/takashito-linode-mcp-server