get_user
Get profile details for a Codebeamer user by their numeric ID.
This record as markdown: /tools/3knightcz-codebeamer-mcp/get-user.md
What get_user does on Codebeamer
AI agents call get_user to retrieve information from Codebeamer without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_user is rated Low
This tool retrieves user profile information by ID without creating, modifying, deleting, or executing anything. It is a straightforward data retrieval with no blast radius risk if misused by an AI agent, as it only exposes already-accessible user metadata. Severity is low because user profile data is typically non-sensitive in most ALM systems, and reading it poses minimal risk.
From the tool's definition Tool description explicitly states 'Get profile details' — a retrieval operation with no modification or side effects. The verb 'Get' and the passive action of querying user profile data confirm this is a read-only operation.
Attacks that exploit this kind of access
The rule that runs get_user safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Codebeamer, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_user, this is the rule to start with:
get_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 Codebeamer, apply this rule, and every get_user call is checked against it from then on.
Questions about get_user
Get profile details for a Codebeamer user by their numeric ID. It is categorised as a Read tool in the Codebeamer MCP Server, which means it retrieves data without modifying state.
Register the Codebeamer MCP server in PolicyLayer and add a rule for get_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 Codebeamer. Nothing to install.
get_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_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_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_user is provided by the Codebeamer MCP server (3knightcz/codebeamer-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Codebeamer, and thousands of servers like it.
This server
Across the catalogue