Write the markdown document for a task. Overwrites any existing content. Use this to persist: investigation findings and research, technical documentation (architecture, APIs, schemas), functional documentation (requirements, acceptance criteria, user flows), root cause analysis and debugging log...
AI agents use karea_set_markdown to create or update resources in Karea — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Karea environment.
This tool creates or modifies task documentation reversibly. While it uses 'Overwrites', the description explicitly recommends reading first and appending rather than replacing, and the content is not permanently destructive—markdown can be rewritten/recovered. The blast radius is medium: an agent could corrupt task documentation, but this is recoverable via version history or re-writing.
From the tool's definition 'Write the markdown document for a task. Overwrites any existing content.' The tool modifies task documentation by writing/overwriting markdown content.
Risk signalsBulk/mass operation — affects multiple targets · Admin/system-level operation
Attacks that exploit this kind of access
Write the markdown document for a task. Overwrites any existing content. Use this to persist: investigation findings and research, technical documentation (architecture, APIs, schemas), functional documentation (requirements, acceptance criteria, user flows), root cause analysis and debugging logs, solution design — planned or implemented, risks, trade-offs, and open questions. This is the single source of truth for everything learned about this task. Always append to existing content (read first with karea_get_markdown) rather than replacing it, unless restructuring. It is categorised as a Write tool in the Karea MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Karea MCP server in PolicyLayer and add a rule for karea_set_markdown: 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 Karea. Nothing to install.
karea_set_markdown 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 karea_set_markdown 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 karea_set_markdown. 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.
karea_set_markdown is provided by the Karea MCP server (starecz/karea-mcp). 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 →