get_user_info

What get_user_info does on QuintaDB

AI agents call get_user_info to retrieve information from QuintaDB without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_user_info is rated Low

The tool queries and returns user account information without creating, modifying, or deleting anything. It is a straightforward data retrieval operation characteristic of Read category tools. Severity is low because the data scope is limited to the authenticated user's own metadata, which poses minimal risk even if accessed inappropriately.

From the tool's definition Tool name 'get_user_info' and description indicate retrieval of user metadata: 'Повернути інформацію про поточного користувача (email, plan, кількість проєктів/записів)' translates to 'Return information about the current user (email, plan, number of…

The rule that runs get_user_info safely

PolicyLayer is an MCP gateway: it sits between your AI agents and QuintaDB, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_user_info, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_user_info": {}
  }
}

Questions about get_user_info