incident.report | PolicyLayer

WHAT IT DOES

What incident.report does on OPTIX: Operational Platform for Threat Intelligence Exploration

AI agents use incident.report to create or update resources in OPTIX: Operational Platform for Threat Intelligence Exploration — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OPTIX: Operational Platform for Threat Intelligence Exploration environment.

WHY IT NEEDS A POLICY

Why incident.report needs a policy

The tool submits (creates) a new incident report in the OPTIX platform. This is a Write operation — it creates a new record/document. However, it carries high severity because incident reports in a threat intelligence platform can trigger downstream workflows, alerting, and tactical responses based on the submitted content. Misuse could flood the system with false incident reports or manipulate triage priorities.

From the tool's definition Submit a structured incident report to OPTIX and generate a tactical intelligence

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

incident.report Rate-limited

incident.report 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "incident.report": {
      "limits": [
        {
          "counter": "incident.report_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches OPTIX: Operational Platform for Threat Intelligence Exploration, so you can run agents against it safely.

FAQ

Questions about incident.report

What does the incident.report tool do? +

Submit a structured incident report to OPTIX and generate a tactical intelligence. It is categorised as a Write tool in the OPTIX: Operational Platform for Threat Intelligence Exploration MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on incident.report? +

Register the OPTIX: Operational Platform for Threat Intelligence Exploration MCP server in PolicyLayer and add a rule for incident.report: 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 OPTIX: Operational Platform for Threat Intelligence Exploration. Nothing to install.

What risk level is incident.report? +

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

Can I rate-limit incident.report? +

Yes. Add a rate_limit block to the incident.report 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 incident.report completely? +

Set action: deny in the PolicyLayer policy for incident.report. 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 incident.report? +

incident.report is provided by the OPTIX: Operational Platform for Threat Intelligence Exploration MCP server (AdamWaldie/OPTIX-MCP). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.