Validate compose secrets match vault. Returns missing/extra secrets per app. This checks that docker-compose secret references have matching entries in the vault.
AI agents call fleet_secrets_validate to retrieve information from Fleet without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs validation by comparing and returning information about secrets (missing/extra secrets per app). It retrieves and reports data about vault state without modifying secrets, deleting them, or executing operations.
From the tool's definition Tool description states it 'Validate compose secrets match vault. Returns missing/extra secrets per app.' The verb 'validate' and 'returns' indicate read-only querying of secret configurations and vault state, with no modification or deletion mentioned.
Documented attack patterns abuse exactly the kind of access fleet_secrets_validate gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Fleet, and nothing reaches the server without passing your rules. This is the rule we recommend for fleet_secrets_validate:
{
"version": "1",
"default": "deny",
"tools": {
"fleet_secrets_validate": {}
}
}fleet_secrets_validate 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 compose secrets match vault. Returns missing/extra secrets per app. This checks that docker-compose secret references have matching entries in the vault. It is categorised as a Read tool in the Fleet MCP Server, which means it retrieves data without modifying state.
Register the Fleet MCP server in PolicyLayer and add a rule for fleet_secrets_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 Fleet. Nothing to install.
fleet_secrets_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 fleet_secrets_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 fleet_secrets_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.
fleet_secrets_validate is provided by the Fleet MCP server (wrxck/fleet). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Fleet, 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.
39 Fleet tools catalogued and risk-classified — across an index of 43,000+ MCP servers.