add_incident_tags

THE RISK

Medium Risk

Why add_incident_tags needs a policy

This tool creates or modifies incident tags, which are metadata annotations. While tags can be added, they are typically removable, making this a Write operation rather than Destructive. The severity is medium because misuse could cause confusion in incident tracking and categorization, potentially affecting security response effectiveness, but it doesn't delete data or execute arbitrary code.

From the tool's definition Tool name is 'add_incident_tags' and description states it will 'Add custom tags to an incident' — this is a reversible modification to incident metadata within the security response workflow.

Documented attack patterns abuse exactly the kind of access add_incident_tags gives an agent:

POLICY

How to control add_incident_tags

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_tags:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_incident_tags": {
      "limits": [
        {
          "counter": "add_incident_tags_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

add_incident_tags 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.

Create a free account and register Response MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Response MCP Server tools

Destructive disable_ad_account Disable an Active Directory user account through Microsoft Defender for Identity. Use when Execute force_ad_password_reset Force an Active Directory user to change their password at next logon through Microsoft De Execute remove_code_restriction Remove code execution restrictions from a device, allowing all applications to run again. Execute revoke_entra_sessions Revoke all Entra ID (Azure AD) sign-in sessions and refresh tokens for a user. Forces re-a Execute run_antivirus_scan Initiate a Microsoft Defender Antivirus scan on a device. Quick scan checks common malware Execute stop_and_quarantine Stop a running process and quarantine the associated file on a device. Requires the SHA1 h Execute isolate_multiple Isolate multiple devices from the network in a single operation. Provide a comma-separated Execute collect_investigation_package Collect a forensic investigation package from a device containing system information, logs

All 23 Response MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about add_incident_tags

What does the add_incident_tags tool do? +

Add custom tags to an incident for categorization and tracking. 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.

How do I enforce a policy on add_incident_tags? +

Register the Response MCP Server MCP server in PolicyLayer and add a rule for add_incident_tags: 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.

What risk level is add_incident_tags? +

add_incident_tags is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_incident_tags? +

Yes. Add a rate_limit block to the add_incident_tags 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.

How do I block add_incident_tags completely? +

Set action: deny in the PolicyLayer policy for add_incident_tags. 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.

What MCP server provides add_incident_tags? +

add_incident_tags 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.

Enforce policy on every Response MCP Server tool call.

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.

CHECK YOUR STACK →