spike_update_confidence · Hedgehog MCP: Risk & Policy

WHAT IT DOES

What spike_update_confidence does on Hedgehog

AI agents use spike_update_confidence 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_update_confidence needs a policy

Without a description, classification relies on the tool name and server context. The 'update' prefix indicates data modification (Write category). The confidence field in technical spike investigations is domain-specific metadata that can be changed but is reversible, placing this firmly in Write rather than Execute or Destructive.

From the tool's definition Tool name is 'spike_update_confidence' with empty description. Sibling tools include 'spike_approve_adr', 'spike_approve_meta', and 'spike_checkpoint', indicating this server manages state modifications.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

spike_update_confidence Rate-limited

spike_update_confidence 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_update_confidence": {
      "limits": [
        {
          "counter": "spike_update_confidence_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_update_confidence

What does the spike_update_confidence tool do? +

spike_update_confidence. 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_update_confidence? +

Register the Hedgehog MCP server in PolicyLayer and add a rule for spike_update_confidence: 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_update_confidence? +

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

Can I rate-limit spike_update_confidence? +

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

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

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