adaptercloud_auth_get_current_user
Fetch the authenticated user via the SDK me query (id, email, username, isActive, emailVerified). Lighter than auth_profile_get and matches the SDK shape. Use auth_status to check authentication state locally without a network round-trip.
This record as markdown: /tools/burdenoff-adaptercloud-mcp/adaptercloud-auth-get-current-user.md
What adaptercloud_auth_get_current_user does on Adaptercloud
AI agents call adaptercloud_auth_get_current_user to retrieve information from Adaptercloud without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why adaptercloud_auth_get_current_user is rated Low
Even though adaptercloud_auth_get_current_user only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs adaptercloud_auth_get_current_user safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Adaptercloud, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adaptercloud_auth_get_current_user, this is the rule to start with:
adaptercloud_auth_get_current_user 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 Adaptercloud, apply this rule, and every adaptercloud_auth_get_current_user call is checked against it from then on.
Questions about adaptercloud_auth_get_current_user
Fetch the authenticated user via the SDK me query (id, email, username, isActive, emailVerified). Lighter than auth_profile_get and matches the SDK shape. Use auth_status to check authentication state locally without a network round-trip. It is categorised as a Read tool in the Adaptercloud MCP Server, which means it retrieves data without modifying state.
Register the Adaptercloud MCP server in PolicyLayer and add a rule for adaptercloud_auth_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 Adaptercloud. Nothing to install.
adaptercloud_auth_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 adaptercloud_auth_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 adaptercloud_auth_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.
adaptercloud_auth_get_current_user is provided by the Adaptercloud MCP server (@burdenoff/adaptercloud-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Adaptercloud, and thousands of servers like it.
This server
Across the catalogue