getCurrentUser
Return the calling user's identity (user_id, display_name, full_name, email, avatar_url). Use this when the user says 'me' / 'mine' / 'I' so you can resolve to their UUID before passing it to tools like updateImprovement(owner_id=…) or filtering by owner. Read-only.
This record as markdown: /tools/io-stablebaseline-sb/getcurrentuser.md
What getCurrentUser does on Stable Baseline
AI agents call getCurrentUser to retrieve information from Stable Baseline without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why getCurrentUser is rated Low
This tool retrieves user identity information without side effects or modifications. It is a pure read operation used to resolve user references for subsequent tool calls. No data is created, modified, deleted, executed, or financially impacted. The explicit 'Read-only' designation confirms its read-only nature.
From the tool's definition Tool name 'getCurrentUser' and description explicitly states 'Return the calling user's identity' and 'Read-only.' Returns user metadata (user_id, display_name, full_name, email, avatar_url) with no modification capabilities.
Attacks that exploit this kind of access
The rule that runs getCurrentUser safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stable Baseline, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getCurrentUser, this is the rule to start with:
getCurrentUser 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 Stable Baseline, apply this rule, and every getCurrentUser call is checked against it from then on.
Questions about getCurrentUser
Return the calling user's identity (user_id, display_name, full_name, email, avatar_url). Use this when the user says 'me' / 'mine' / 'I' so you can resolve to their UUID before passing it to tools like updateImprovement(owner_id=…) or filtering by owner. Read-only. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
Register the Stable Baseline MCP server in PolicyLayer and add a rule for getCurrentUser: 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 Stable Baseline. Nothing to install.
getCurrentUser 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 getCurrentUser 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 getCurrentUser. 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.
getCurrentUser is provided by the Stable Baseline MCP server (https://api.stablebaseline.io/functions/v1/cloud-serve/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stable Baseline, and thousands of servers like it.
This server
Across the catalogue