Get tool schema with examples and accepted formats
AI agents call describe_tool_vast to retrieve information from VAST Admin MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a metadata/introspection tool that queries and returns information about tool schemas. It performs a read-only operation with no side effects, reversible actions, code execution, data destruction, or financial implications. The blast radius of misuse is minimal—an agent could only access documentation and schema information already available through the MCP server interface.
From the tool's definition Tool name and description indicate it retrieves tool schema information with examples and accepted formats. Keywords: 'Get' (retrieval), 'schema' (metadata query). No modification, deletion, execution, or financial impact.
Documented attack patterns abuse exactly the kind of access describe_tool_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 describe_tool_vast:
{
"version": "1",
"default": "deny",
"tools": {
"describe_tool_vast": {}
}
} describe_tool_vast is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get tool schema with examples and accepted formats. It is categorised as a Read tool in the VAST Admin MCP Server MCP Server, which means it retrieves data without modifying state.
Register the VAST Admin MCP Server MCP server in PolicyLayer and add a rule for describe_tool_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.
describe_tool_vast 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 describe_tool_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 describe_tool_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.
describe_tool_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.