get_item
Get a lightweight summary of a Codebeamer work item: ID, name, tracker, status and description.
This record as markdown: /tools/3knightcz-codebeamer-mcp/get-item.md
What get_item does on Codebeamer
AI agents call get_item 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_item is rated Low
The tool queries and returns existing item information without creating, modifying, deleting, or executing any operations. This is a straightforward data retrieval operation with no destructive or side-effect capability, placing it firmly in the Read category with low severity.
From the tool's definition Tool retrieves a 'lightweight summary' of item data (ID, name, tracker, status, description) with no modification or side effects described.
Attacks that exploit this kind of access
The rule that runs get_item 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_item, this is the rule to start with:
get_item 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_item call is checked against it from then on.
Questions about get_item
Get a lightweight summary of a Codebeamer work item: ID, name, tracker, status and description. 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_item: 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_item 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_item 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_item. 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_item 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