Creates a Decision node in the graph. Call this when making or discovering architectural choices. Returns a status string. Phase 9: pass corroborates=<id> to reinforce, supersedes=<id> to replace, or force=true to bypass duplicate detection.
AI agents use record_decision to create or update resources in Memex — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Memex environment.
This tool writes new data (Decision nodes) to the knowledge graph, and can also modify existing relationships via corroboration or supersession. It is reversible in principle (nodes can be invalidated or replaced), so Write is more appropriate than Destructive. Misuse could corrupt the architectural decision record used by AI agents, leading to bad code suggestions — medium severity.
From the tool's definition Creates a Decision node in the graph... pass corroborates=<id> to reinforce, supersedes=<id> to replace, or force=true to bypass duplicate detection
Documented attack patterns abuse exactly the kind of access record_decision gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Memex, and nothing reaches the server without passing your rules. This is the rule we recommend for record_decision:
{
"version": "1",
"default": "deny",
"tools": {
"record_decision": {
"limits": [
{
"counter": "record_decision_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}record_decision 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.
Free to start. No card required.
Creates a Decision node in the graph. Call this when making or discovering architectural choices. Returns a status string. Phase 9: pass corroborates=<id> to reinforce, supersedes=<id> to replace, or force=true to bypass duplicate detection. It is categorised as a Write tool in the Memex MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Memex MCP server in PolicyLayer and add a rule for record_decision: 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 Memex. Nothing to install.
record_decision 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 record_decision 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 record_decision. 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.
record_decision is provided by the Memex MCP server (stifler7/memex). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Memex, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 Memex tools catalogued and risk-classified — across an index of 43,000+ MCP servers.