Get information about the authenticated user. This tool retrieves your Dooray member profile using your API token. Most importantly, it returns your member ID which is needed for other operations like filtering tasks by assignee. No parameters needed - it automatically uses your authentication to...
AI agents call get-my-member-info to retrieve information from Dooray MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and retrieves authenticated user profile information without creating, modifying, deleting, or executing any operations. It is a straightforward Read operation with minimal blast radius—at worst, an agent learns the user's member ID and profile details, which are already accessible to authenticated users. The lack of parameters and purely informational purpose confirm low severity.
From the tool's definition Tool name 'get-my-member-info' and description 'retrieves your Dooray member profile' and 'returns your member ID' indicate pure data retrieval with no side effects.
Attacks that exploit this kind of access
Get information about the authenticated user. This tool retrieves your Dooray member profile using your API token. Most importantly, it returns your member ID which is needed for other operations like filtering tasks by assignee. No parameters needed - it automatically uses your authentication token. Examples: - Get my info: {} (empty parameters) -. It is categorised as a Read tool in the Dooray MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Dooray MCP Server MCP server in PolicyLayer and add a rule for get-my-member-info: 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 Dooray MCP Server. Nothing to install.
get-my-member-info 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-my-member-info 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-my-member-info. 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-my-member-info is provided by the Dooray MCP Server MCP server (jhl8041/dooray-mcp). 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 →