特定のサービスのラベルを更新します。
AI agents use waroom_update_service_label 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.
The tool modifies existing service label data. While the change is reversible (can be updated again), it affects service metadata and could impact incident categorization, filtering, or organizational processes. It is not a read-only operation (which would be Read), not destructive (deletion would be Destructive), not executable code (which would be Execute), and not financial. Write is the appropriate category.
From the tool's definition Tool name contains 'update' and description states it updates/modifies service labels (「ラベルを更新します」= 'updates labels'). This is a reversible modification operation.
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_update_service_label: 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_update_service_label 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_update_service_label 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_update_service_label. 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_update_service_label 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 →