create_harm
Create a new item in a Codebeamer RM Harms List tracker.
This record as markdown: /tools/3knightcz-codebeamer-mcp/create-harm.md
What create_harm does on Codebeamer
AI agents use create_harm to create or update resources in Codebeamer, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Codebeamer environment.
Why create_harm is rated Medium
This tool creates a new item in a tracker, which is a reversible write operation. While 'harms' in the context of Requirements Management (RM) suggests safety-critical documentation, the tool itself performs data creation, not execution of harm or deletion.
From the tool's definition Tool name 'create_harm' and description 'Create a new item in a Codebeamer RM Harms List tracker' indicate data creation.
Attacks that exploit this kind of access
The rule that runs create_harm 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 create_harm, this is the rule to start with:
create_harm stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 create_harm call is checked against it from then on.
Questions about create_harm
Create a new item in a Codebeamer RM Harms List tracker. It is categorised as a Write tool in the Codebeamer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Codebeamer MCP server in PolicyLayer and add a rule for create_harm: 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.
create_harm is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_harm 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 create_harm. 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.
create_harm 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