Validate Docker Compose YAML for TrueNAS compatibility
AI agents call validate_compose to retrieve information from TrueNAS Scale MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs validation/verification of Docker Compose YAML configuration files to check compatibility. Validation is a read-like operation that parses and checks configuration without creating, modifying, executing, or deleting any infrastructure or data. Even if the validator reports errors, it only provides feedback; it does not execute, deploy, or change any actual application state.
From the tool's definition Tool name is 'validate_compose' and description states 'Validate Docker Compose YAML for TrueNAS compatibility'. The word 'validate' indicates a check or verification operation with no modification, deletion, or execution of resources.
Documented attack patterns abuse exactly the kind of access validate_compose gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and TrueNAS Scale MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for validate_compose:
{
"version": "1",
"default": "deny",
"tools": {
"validate_compose": {}
}
}validate_compose 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.
Validate Docker Compose YAML for TrueNAS compatibility. It is categorised as a Read tool in the TrueNAS Scale MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TrueNAS Scale MCP Server MCP server in PolicyLayer and add a rule for validate_compose: 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 TrueNAS Scale MCP Server. Nothing to install.
validate_compose 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_compose 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_compose. 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_compose is provided by the TrueNAS Scale MCP Server MCP server (svnstfns/truenas-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from TrueNAS Scale 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.
13 TrueNAS Scale MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.