AI agents call users_get_by_email to retrieve information from Remnawave without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user information based on an email parameter. It is a query/fetch operation with no side effects, matching the 'Read' category definition. Severity is low because retrieving user metadata poses minimal risk even if misused—it returns information that may already be discoverable through other means. The confidence is high because the name and description unambiguously indicate a read-only lookup.
From the tool's definition Tool name 'users_get_by_email' and description 'Get a Remnawave user by their email' indicate a retrieval operation that queries user data by email address without modifying, deleting, or executing external operations.
Documented attack patterns abuse exactly the kind of access users_get_by_email gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Remnawave, and nothing reaches the server without passing your rules. This is the rule we recommend for users_get_by_email:
{
"version": "1",
"default": "deny",
"tools": {
"users_get_by_email": {}
}
}users_get_by_email 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 Remnawave user by their email. It is categorised as a Read tool in the Remnawave MCP Server, which means it retrieves data without modifying state.
Register the Remnawave MCP server in PolicyLayer and add a rule for users_get_by_email: 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 Remnawave. Nothing to install.
users_get_by_email 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 users_get_by_email 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 users_get_by_email. 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.
users_get_by_email is provided by the Remnawave MCP server (trackline/mcp-remnawave). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 153 Remnawave tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
153 Remnawave tools catalogued and risk-classified — across an index of 42,500+ MCP servers.