Validate Kubernetes manifests or Helm values against schema and best-practice policies. Returns structured error/warning results.
AI agents call validate to retrieve information from Agent Zone without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs validation by checking manifests against schemas and policies, then returning structured results. This is a read/analysis operation with no side effects — it does not modify, deploy, or delete any resources. The output is purely informational (errors/warnings), making it a Read category tool with low severity.
From the tool's definition Validate Kubernetes manifests or Helm values against schema and best-practice policies. Returns structured error/warning results.
Attacks that exploit this kind of access
Validate Kubernetes manifests or Helm values against schema and best-practice policies. Returns structured error/warning results. It is categorised as a Read tool in the Agent Zone MCP Server, which means it retrieves data without modifying state.
Register the Agent Zone MCP server in PolicyLayer and add a rule for validate: 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 Agent Zone. Nothing to install.
validate 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 validate 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 validate. 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.
validate is provided by the Agent Zone MCP server (statherm/agent-zone-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →