create_custom_event · HC3 MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_custom_event does on HC3 MCP Server

AI agents use create_custom_event to create or update resources in HC3 MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your HC3 MCP Server environment.

WHY IT NEEDS A POLICY

Why create_custom_event needs a policy

Creating custom events modifies the system's event structure reversibly—events can be deleted or modified later. It does not execute arbitrary code, delete data irreversibly, or move financial resources.

From the tool's definition Tool name 'create_custom_event' and description 'Create a new custom event' indicate creation of new event objects in the HC3 system. This is a data creation operation without explicit deletion or destructive capabilities.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_custom_event Rate-limited

create_custom_event 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": {
    "create_custom_event": {
      "limits": [
        {
          "counter": "create_custom_event_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 HC3 MCP Server, so you can run agents against it safely.

FAQ

Questions about create_custom_event

What does the create_custom_event tool do? +

Create a new custom event. It is categorised as a Write tool in the HC3 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 create_custom_event? +

Register the HC3 MCP Server MCP server in PolicyLayer and add a rule for create_custom_event: 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 HC3 MCP Server. Nothing to install.

What risk level is create_custom_event? +

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

Can I rate-limit create_custom_event? +

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

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

create_custom_event is provided by the HC3 MCP Server MCP server (jangabrielsson/hc3_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.