vaultwarden_user_count
Return the number of registered Vaultwarden users. Requires a valid VAULTWARDEN_ADMIN_TOKEN — the admin API does not expose passwords, only account metadata.
This record as markdown: /tools/kh0pper-crow/vaultwarden-user-count.md
What vaultwarden_user_count does on Crow
AI agents call vaultwarden_user_count to retrieve information from Crow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why vaultwarden_user_count is rated Low
This tool retrieves data (user count) without side effects. It is a simple read operation querying existing account metadata. While it requires elevated permissions (admin token), the action itself is non-destructive and non-reversible data query. Severity is low because exposing user count is a low-impact information disclosure even if accessed unauthorizedly.
From the tool's definition Tool explicitly 'Return[s] the number of registered Vaultwarden users' and 'only account metadata'. No creation, modification, deletion, or financial operations described. Requires admin token but performs a query operation.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs vaultwarden_user_count safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vaultwarden_user_count, this is the rule to start with:
vaultwarden_user_count is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every vaultwarden_user_count call is checked against it from then on.
Questions about vaultwarden_user_count
Return the number of registered Vaultwarden users. Requires a valid VAULTWARDEN_ADMIN_TOKEN — the admin API does not expose passwords, only account metadata. 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_user_count: 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_user_count 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_user_count 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_user_count. 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_user_count 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.
More on Crow, and thousands of servers like it.
This server
Across the catalogue