Return the number of registered Vaultwarden users. Requires a valid VAULTWARDEN_ADMIN_TOKEN — the admin API does not expose passwords, only account metadata.
AI agents call vaultwarden_user_count 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.
This tool queries Vaultwarden admin API to retrieve a count of registered users—a non-sensitive aggregate statistic. It performs no data modification, deletion, or execution of external operations. The requirement for admin token is a security gate, not a category escalator. The blast radius of misuse is minimal: an attacker gains knowledge of user population size, which is low-impact information disclosure.
From the tool's definition Tool name 'vaultwarden_user_count' and description 'Return the number of registered Vaultwarden users' indicates a retrieval operation.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access vaultwarden_user_count 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_user_count:
{
"version": "1",
"default": "deny",
"tools": {
"vaultwarden_user_count": {}
}
} vaultwarden_user_count 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.
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.
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.