Add a comment to a security incident for documentation and collaboration.
AI agents use add_incident_comment to create or update resources in Response MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Response MCP Server environment.
This tool modifies incident records by appending comments, which is a write operation. While comments are additive and reversible (can typically be deleted or edited), they do affect incident state and are part of a high-stakes security context (Microsoft Defender XDR incidents).
From the tool's definition Tool description states 'Add a comment to a security incident' — this creates new data (a comment) within an incident record. The verb 'add' and the action of appending documentation represent a reversible write operation.
Documented attack patterns abuse exactly the kind of access add_incident_comment gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Response MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for add_incident_comment:
{
"version": "1",
"default": "deny",
"tools": {
"add_incident_comment": {
"limits": [
{
"counter": "add_incident_comment_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_incident_comment 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.
Free to start. No card required.
Add a comment to a security incident for documentation and collaboration. It is categorised as a Write tool in the Response MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Response MCP Server MCP server in PolicyLayer and add a rule for add_incident_comment: 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 Response MCP Server. Nothing to install.
add_incident_comment 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 add_incident_comment 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 add_incident_comment. 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.
add_incident_comment is provided by the Response MCP Server MCP server (markolauren/responsemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Response MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
23 Response MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.