Get information about the current authenticated user
AI agents call get_current_user to retrieve information from OpenProject MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries user profile information without modifying, executing operations, or affecting external systems. It is a straightforward read operation that retrieves data about the authenticated user, making it low-risk even if misused by an AI agent—the worst outcome would be unauthorized information disclosure of the user's own profile data.
From the tool's definition Tool name 'get_current_user' and description 'Get information about the current authenticated user' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get information about the current authenticated user. It is categorised as a Read tool in the OpenProject MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OpenProject 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 OpenProject 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 OpenProject MCP Server MCP server (widjis/mcp-openproject). 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 →