インシデントを作成します。
AI agents use waroom_create_incident to create or update resources in Waroom MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Waroom MCP environment.
This tool creates incident records in the Waroom incident management system. While creation is reversible (incidents can typically be deleted), it represents a write operation that adds data to the system. The severity is high because creating false or unauthorized incidents could disrupt incident tracking, trigger alert cascades, or cause operational confusion in a critical incident management platform.
From the tool's definition Tool name is 'waroom_create_incident' and description states it creates incidents ('インシデントを作成します' = 'Creates incidents' in Japanese). The tool name explicitly includes 'create', indicating a write operation that modifies data.
Attacks that exploit this kind of access
インシデントを作成します。. It is categorised as a Write tool in the Waroom MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Waroom MCP server in PolicyLayer and add a rule for waroom_create_incident: 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 Waroom MCP. Nothing to install.
waroom_create_incident 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 waroom_create_incident 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 waroom_create_incident. 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.
waroom_create_incident is provided by the Waroom MCP server (topotal/waroom-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 →