Seal runtime secrets back to the encrypted vault.
AI agents use fleet_secrets_seal to create or update resources in Fleet — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fleet environment.
This tool encrypts and writes secrets back to an age-encrypted vault. It creates/modifies encrypted data (Write), but does not delete existing secrets irreversibly. However, misuse could overwrite valid secrets with corrupted or malicious values, causing high impact on a production environment.
From the tool's definition Seal runtime secrets back to the encrypted vault
Documented attack patterns abuse exactly the kind of access fleet_secrets_seal 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_seal:
{
"version": "1",
"default": "deny",
"tools": {
"fleet_secrets_seal": {
"limits": [
{
"counter": "fleet_secrets_seal_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}fleet_secrets_seal stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Seal runtime secrets back to the encrypted vault. It is categorised as a Write tool in the Fleet MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fleet MCP server in PolicyLayer and add a rule for fleet_secrets_seal: 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_seal is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the fleet_secrets_seal 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_seal. 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_seal 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.