create_support_bundle_vast

THE RISK

High Risk

Why create_support_bundle_vast needs a policy

Creating a support bundle initiates an operation on the cluster (collecting logs, diagnostics, system state) that has side effects but is not purely destructive or financial. It executes a cluster-side process whose scope depends on the cluster state, making Execute the most appropriate category. Severity is medium since it consumes cluster resources and potentially exposes sensitive diagnostic information.

From the tool's definition 'Create a support bundle on a VAST cluster for diagnostics and troubleshooting' — triggers an external operation on the cluster to gather and bundle diagnostic data

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

POLICY

How to control create_support_bundle_vast

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_support_bundle_vast": {
      "limits": [
        {
          "counter": "create_support_bundle_vast_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

create_support_bundle_vast stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register VAST Admin MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More VAST Admin MCP Server tools

Write create_clone_vast Create a clone from a snapshot Write create_quota_vast Create or update quota for a specific path and tenant Write create_snapshot_vast Create a snapshot for a VAST view Write create_view_from_template_vast Create a new VAST view from a predefined template Write create_view_vast Create a new VAST view Read describe_tool_vast Get tool schema with examples and accepted formats Read list_clusters_vast Retrieve information about configured VAST clusters Read list_dataflow_diagram_vast Show dataflow topology as a visual Mermaid diagram: Hosts -> CNodes -> Views with bandwidt

All 16 VAST Admin MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in VAST Admin MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about create_support_bundle_vast

What does the create_support_bundle_vast tool do? +

Create a support bundle on a VAST cluster for diagnostics and troubleshooting. It is categorised as a Execute tool in the VAST Admin MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on create_support_bundle_vast? +

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

What risk level is create_support_bundle_vast? +

create_support_bundle_vast is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit create_support_bundle_vast? +

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

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

create_support_bundle_vast is provided by the VAST Admin MCP Server MCP server (vast-data/vast-admin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every VAST Admin MCP Server tool call.

Start from VAST Admin MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →