Get the current authenticated NDB user. Returns user details for the account associated with the current authentication context (API token or username/password). Returned fields: - id: User ID - username: Login name - email: Email address (if available) - isExternalAuth: True if authenticated via...
AI agents call get_current_user to retrieve information from NDB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward read operation that queries and returns user identity and metadata from the current authentication context. It performs no mutations, deletions, executions, or financial transactions. The use case mentioned ('audit') further confirms it is informational. Severity is low because disclosure of user metadata has limited blast radius compared to more sensitive operations on the platform.
From the tool's definition Tool name is 'get_current_user' and description states it 'Get the current authenticated NDB user. Returns user details' — purely a retrieval operation with no side effects. Returns read-only fields: id, username, email, isExternalAuth, passwordExpired, roles.
Attacks that exploit this kind of access
Get the current authenticated NDB user. Returns user details for the account associated with the current authentication context (API token or username/password). Returned fields: - id: User ID - username: Login name - email: Email address (if available) - isExternalAuth: True if authenticated via external directory (e.g., Active Directory) - passwordExpired: True if password is expired - roles: Array of assigned roles (uuid), should be used with list_roles tools to get the role name Use Cases: - Identify the current user context for audit or troubleshooting - Display user information in UI or logs - Validate authentication and permissions. It is categorised as a Read tool in the NDB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the NDB MCP Server MCP server in PolicyLayer and add a rule for get_current_user: 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 NDB MCP Server. Nothing to install.
get_current_user 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_current_user 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_current_user. 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_current_user is provided by the NDB MCP Server MCP server (rouxton/ndb-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →