AI agents use spike_generate_adr 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.
ADR generation creates new documents in a persistent system, modifying the state of the technical spike investigation. This is a Write operation—it produces new data structures that persist. Severity is medium because ADRs guide architecture decisions but don't directly execute code, delete data, or move funds.
From the tool's definition Tool name 'spike_generate_adr' suggests generating Architecture Decision Records (ADRs). The server description indicates it 'generates Architecture Decision Records through an enforced four-phase workflow' and 'maintain[s] persistent state.' The tool…
Attacks that exploit this kind of access
spike_generate_adr. 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_generate_adr: 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_generate_adr 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_generate_adr 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_generate_adr. 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_generate_adr 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 →