spike_checkpoint · Hedgehog MCP: Risk & Policy

WHAT IT DOES

What spike_checkpoint does on Hedgehog

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

WHY IT NEEDS A POLICY

Why spike_checkpoint needs a policy

The tool creates (writes) a snapshot of spike investigation state, which is a reversible operation. It does not execute arbitrary code, delete data, or move money. It aligns with Write category as it creates/records data without destructive side effects. Severity is low because checkpointing is a non-critical operation with minimal blast radius if misused by an agent.

From the tool's definition Tool name 'spike_checkpoint' and description 'Create a checkpoint of the current spike state' indicate creating/saving state data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

spike_checkpoint Rate-limited

spike_checkpoint 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": {
    "spike_checkpoint": {
      "limits": [
        {
          "counter": "spike_checkpoint_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 Hedgehog, so you can run agents against it safely.

FAQ

Questions about spike_checkpoint

What does the spike_checkpoint tool do? +

Create a checkpoint of the current spike state. It is categorised as a Write tool in the Hedgehog MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on spike_checkpoint? +

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

What risk level is spike_checkpoint? +

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

Can I rate-limit spike_checkpoint? +

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

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

spike_checkpoint is provided by the Hedgehog MCP server (jpalmerr/hedgehog). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.