AI agents use create_view_vast to create or update resources in VAST Admin MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your VAST Admin MCP Server environment.
This tool creates a new view, which is a reversible write operation that modifies the cluster configuration by adding a new logical data container. It does not delete data, execute arbitrary code, or involve financial transactions. The severity is medium because creating views could impact storage organization and access patterns, but the operation is reversible through deletion if needed.
From the tool's definition Tool name contains 'create_view' and description states 'Create a new VAST view', indicating creation of new data storage/organizational structures within the VAST cluster.
Documented attack patterns abuse exactly the kind of access create_view_vast gives an agent:
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_view_vast:
{
"version": "1",
"default": "deny",
"tools": {
"create_view_vast": {
"limits": [
{
"counter": "create_view_vast_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_view_vast stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new VAST view. It is categorised as a Write tool in the VAST Admin MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the VAST Admin MCP Server MCP server in PolicyLayer and add a rule for create_view_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.
create_view_vast is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_view_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.
Set action: deny in the PolicyLayer policy for create_view_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.
create_view_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.
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.
Free to start. No card required.
16 VAST Admin MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.