AI agents use arch_record_lesson to create or update resources in Paparats — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Paparats environment.
The name implies writing/storing a lesson learned to the architecture knowledge base. With no description to confirm, confidence is low. Sibling tools like 'arch_record_component' and 'arch_record_decision' also follow a write pattern, suggesting this tool similarly creates/updates records. Classified as Write with medium severity due to potential to add misleading architectural knowledge.
From the tool's definition Tool name 'arch_record_lesson' — 'record' suggests creating or storing data; no description provided.
Attacks that exploit this kind of access
arch_record_lesson. It is categorised as a Write tool in the Paparats MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Paparats MCP server in PolicyLayer and add a rule for arch_record_lesson: 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 Paparats. Nothing to install.
arch_record_lesson 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 arch_record_lesson 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 arch_record_lesson. 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.
arch_record_lesson is provided by the Paparats MCP server (@paparats/cli). 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 →