AI agents use spike_create 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.
The tool name 'spike_create' combined with the server's purpose of managing technical spike investigations suggests this tool creates new spike records or investigations. This is a Write operation (creates data reversibly). Without an explicit description, confidence is moderate but justified by naming convention and context.
From the tool's definition Tool name is 'spike_create' which indicates creation of a new entity. The server manages 'structured technical spike investigations' and sibling tools include operations like spike_add_branch, spike_add_challenge, spike_checkpoint, and spike_generate_adr.
Attacks that exploit this kind of access
spike_create. 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.
Register the Hedgehog MCP server in PolicyLayer and add a rule for spike_create: 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.
spike_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the spike_create 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.
Set action: deny in the PolicyLayer policy for spike_create. 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.
spike_create 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →