Low Risk

get_disk

get_disk

How to control get_disk ↓

What get_disk does on Sacloud

AI agents call get_disk to retrieve information from Sacloud without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_disk needs a policy

The tool name 'get_disk' suggests retrieval of disk information or properties from Sakura Cloud infrastructure. The 'get' verb pattern is standard for read-only queries that retrieve data without side effects. While the empty description reduces confidence somewhat, the naming convention clearly indicates this is a data retrieval tool rather than a write, execute, or destructive operation.

From the tool's definition Tool name 'get_disk' follows the 'get' pattern which conventionally retrieves data without modification. The empty description limits certainty, but the verb 'get' strongly indicates a read operation.

Documented attack patterns abuse exactly the kind of access get_disk gives an agent:

How to control get_disk

PolicyLayer is an MCP gateway — it sits between your AI agents and Sacloud, and nothing reaches the server without passing your rules. This is the rule we recommend for get_disk:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_disk": {}
  }
}

get_disk is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Sacloud — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_disk

What does the get_disk tool do? +

get_disk. It is categorised as a Read tool in the Sacloud MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_disk? +

Register the Sacloud MCP server in PolicyLayer and add a rule for get_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 Sacloud. Nothing to install.

What risk level is get_disk? +

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

Can I rate-limit get_disk? +

Yes. Add a rate_limit block to the get_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.

How do I block get_disk completely? +

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

What MCP server provides get_disk? +

get_disk is provided by the Sacloud MCP server (sacloud/sacloud-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Sacloud tool call.

Start from Sacloud, 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.

37 Sacloud tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.