get_user_info
Get information about the authenticated user
This record as markdown: /tools/3xcaffeine-mcp-server/get-user-info.md
What get_user_info does on VaultAssist
AI agents call get_user_info to retrieve information from VaultAssist 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
This tool queries user profile information (name, email, account details, etc.) with no side effects. It is a straightforward read operation. The 'authenticated user' context implies it accesses only the current user's own information, limiting blast radius. Severity is low because user info exposure has minimal direct impact compared to email deletion, financial transactions, or code execution.
From the tool's definition Tool name 'get_user_info' and description 'Get information about the authenticated user' indicate a read-only operation that retrieves user metadata without modifying or executing anything.
Attacks that exploit this kind of access
The rule that runs get_user_info safely
PolicyLayer is an MCP gateway: it sits between your AI agents and VaultAssist, 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:
get_user_info 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 VaultAssist, apply this rule, and every get_user_info call is checked against it from then on.
Questions about get_user_info
Get information about the authenticated user. It is categorised as a Read tool in the VaultAssist MCP Server, which means it retrieves data without modifying state.
Register the VaultAssist MCP server in PolicyLayer and add a rule for get_user_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 VaultAssist. Nothing to install.
get_user_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 get_user_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 get_user_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.
get_user_info is provided by the VaultAssist MCP server (3xcaffeine/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on VaultAssist, and thousands of servers like it.
This server
Across the catalogue