list_machine_releases

List published releases, newest version first. Omit sandboxId to list every release in the account.

SERVEREasyBits SOURCE@easybits.cloud/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/cloud-easybits-easybits/list-machine-releases.md

WHAT IT DOES

What list_machine_releases does on EasyBits

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

RISK

Why list_machine_releases is rated Low

Retrieves release metadata without modifying data or executing operations.

From the tool's definition List published releases, newest version first. Omit sandboxId.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_machine_releases safely

PolicyLayer is an MCP gateway: it sits between your AI agents and EasyBits, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_machine_releases, this is the rule to start with:

list_machine_releases Allowed

list_machine_releases is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_machine_releases": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect EasyBits, apply this rule, and every list_machine_releases call is checked against it from then on.

FAQ

Questions about list_machine_releases

What does the list_machine_releases tool do? +

List published releases, newest version first. Omit sandboxId to list every release in the account. It is categorised as a Read tool in the EasyBits MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_machine_releases? +

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

What risk level is list_machine_releases? +

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

Can I rate-limit list_machine_releases? +

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

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

list_machine_releases is provided by the EasyBits MCP server (@easybits.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on EasyBits, and thousands of servers like it.

This server

All 273 EasyBits tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →