vm_available_memory
Get the amount of memory available for allocating to VMs, in bytes.
This record as markdown: /tools/nasbridge/vm-available-memory.md
What vm_available_memory does on Nasbridge
AI agents call vm_available_memory to retrieve information from Nasbridge without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why vm_available_memory is rated Low
This tool performs a simple data retrieval operation to check available memory resources. It has no side effects, cannot modify system state, and poses minimal risk if an AI agent calls it. The worst outcome is retrieving accurate or inaccurate memory information, which does not cause harm.
From the tool's definition Tool name 'vm_available_memory' and description 'Get the amount of memory available for allocating to VMs, in bytes' indicate a read-only query operation that retrieves system information without modifying, executing, or deleting any data.
Attacks that exploit this kind of access
The rule that runs vm_available_memory safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nasbridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vm_available_memory, this is the rule to start with:
vm_available_memory is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nasbridge, apply this rule, and every vm_available_memory call is checked against it from then on.
Questions about vm_available_memory
Get the amount of memory available for allocating to VMs, in bytes. It is categorised as a Read tool in the Nasbridge MCP Server, which means it retrieves data without modifying state.
Register the Nasbridge MCP server in PolicyLayer and add a rule for vm_available_memory: 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 Nasbridge. Nothing to install.
vm_available_memory 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 vm_available_memory 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 vm_available_memory. 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.
vm_available_memory is provided by the Nasbridge MCP server (maverick0628/nasbridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nasbridge, and thousands of servers like it.
This server
Across the catalogue