Get a single decrypted secret value from the vault.
AI agents call fleet_secrets_get 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 retrieves secrets from a vault without modifying them, making it a Read operation. However, severity is high because: (1) secrets often include credentials, API keys, and encryption material whose exposure could compromise production systems, (2) the decryption aspect indicates access to sensitive protected data, and (3) in a production Docker Compose environment with systemd and Nginx orchestration,…
From the tool's definition Tool name 'fleet_secrets_get' and description 'Get a single decrypted secret value from the vault' indicate retrieval of sensitive data with no modification.
Documented attack patterns abuse exactly the kind of access fleet_secrets_get 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_get:
{
"version": "1",
"default": "deny",
"tools": {
"fleet_secrets_get": {}
}
}fleet_secrets_get 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 a single decrypted secret value from 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_get: 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_get 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_get 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_get. 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_get 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.