user_get_current

Get the current authenticated user's information.

Server Semaphore vitexsoftware/semaphore-mcp-server
Category Read
Risk class Low
Parameters 00 required

What user_get_current does on Semaphore

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

Why user_get_current needs a policy

This tool queries and returns information about the authenticated user. It performs a read-only operation that does not modify, delete, execute, or create any data. The retrieval of user metadata poses minimal security risk as it only exposes information about the caller themselves.

From the tool's definition Tool name 'user_get_current' and description 'Get the current authenticated user's information' indicate a retrieval operation with no side effects.

Questions about user_get_current

What does the user_get_current tool do? +

Get the current authenticated user's information. It is categorised as a Read tool in the Semaphore MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on user_get_current? +

Register the Semaphore MCP server in PolicyLayer and add a rule for user_get_current: 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 Semaphore. Nothing to install.

What risk level is user_get_current? +

user_get_current is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit user_get_current? +

Yes. Add a rate_limit block to the user_get_current 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.

How do I block user_get_current completely? +

Set action: deny in the PolicyLayer policy for user_get_current. 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.

What MCP server provides user_get_current? +

user_get_current is provided by the Semaphore MCP server (vitexsoftware/semaphore-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.