Record an architectural or technical decision in pmpt.md. Use this when making important choices (tech stack, library selection, design patterns, etc.) so the reasoning is preserved.
AI agents use pmpt_log_decision to create or update resources in Pmpt — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pmpt environment.
The tool creates or modifies documentation by recording decision entries in pmpt.md. This is a Write operation (creates/modifies data reversibly) rather than Read (query-only), Execute (code/command execution), or Destructive (irreversible deletion). The decision log can be edited or removed, making it reversible.
From the tool's definition Tool description states 'Record an architectural or technical decision in pmpt.md', which is a create/modify operation that adds entries to a markdown file. The word 'Record' combined with the pmpt wiki context indicates reversible data creation.
Documented attack patterns abuse exactly the kind of access pmpt_log_decision gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pmpt, and nothing reaches the server without passing your rules. This is the rule we recommend for pmpt_log_decision:
{
"version": "1",
"default": "deny",
"tools": {
"pmpt_log_decision": {
"limits": [
{
"counter": "pmpt_log_decision_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}pmpt_log_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.
Record an architectural or technical decision in pmpt.md. Use this when making important choices (tech stack, library selection, design patterns, etc.) so the reasoning is preserved. It is categorised as a Write tool in the Pmpt MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pmpt MCP server in PolicyLayer and add a rule for pmpt_log_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 Pmpt. Nothing to install.
pmpt_log_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 pmpt_log_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 pmpt_log_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.
pmpt_log_decision is provided by the Pmpt MCP server (pmptwiki/pmpt-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Pmpt, 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.
14 Pmpt tools catalogued and risk-classified — across an index of 43,000+ MCP servers.