Report the size and modification time of the Vaultwarden data directory (for backup freshness checks). Does NOT read vault contents.
AI agents call vaultwarden_backup_info to retrieve information from Crow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves only file system metadata (size and modification timestamp) about a backup directory to check freshness. It performs no mutation, deletion, execution, or financial operation. The explicit disclaimer that it does not read vault contents further confirms this is a safe read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool description states it 'Report[s] the size and modification time of the Vaultwarden data directory' and explicitly clarifies 'Does NOT read vault contents.' This is a metadata query operation with no side effects.
Documented attack patterns abuse exactly the kind of access vaultwarden_backup_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for vaultwarden_backup_info:
{
"version": "1",
"default": "deny",
"tools": {
"vaultwarden_backup_info": {}
}
}vaultwarden_backup_info 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.
Report the size and modification time of the Vaultwarden data directory (for backup freshness checks). Does NOT read vault contents. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.
Register the Crow MCP server in PolicyLayer and add a rule for vaultwarden_backup_info: 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 Crow. Nothing to install.
vaultwarden_backup_info 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 vaultwarden_backup_info 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 vaultwarden_backup_info. 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.
vaultwarden_backup_info is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Crow, 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.
576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.