append_to_daily_note

THE RISK

Medium Risk

Why append_to_daily_note needs a policy

This tool appends (adds) content to a daily note, which is a reversible write operation. It does not delete or overwrite existing data, execute code, or involve financial transactions. The blast radius is low since it only adds markdown text to a personal note.

From the tool's definition Append/capture markdown to a daily note

Documented attack patterns abuse exactly the kind of access append_to_daily_note gives an agent:

POLICY

How to control append_to_daily_note

PolicyLayer is an MCP gateway — it sits between your AI agents and Roam, and nothing reaches the server without passing your rules. This is the rule we recommend for append_to_daily_note:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "append_to_daily_note": {
      "limits": [
        {
          "counter": "append_to_daily_note_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

append_to_daily_note 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.

Create a free account and register Roam — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Roam tools

Destructive delete_block Delete a block Destructive delete_page Delete a page Destructive file_delete Delete a file hosted on Roam Execute datalog_query Execute a raw Datalog query against the graph's Datomic database Execute roam_query Execute a Roam query ({{query:}} blocks, not Datalog) Execute open_main_window Navigate to page/block Execute open_sidebar Open in right sidebar Write add_comment Add a comment to a block (comment thread, not child block)

All 27 Roam tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about append_to_daily_note

What does the append_to_daily_note tool do? +

Append/capture markdown to a daily note (today by default, or MM-DD-YYYY / today/yesterday/tomorrow; optional nest-under section). It is categorised as a Write tool in the Roam MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on append_to_daily_note? +

Register the Roam MCP server in PolicyLayer and add a rule for append_to_daily_note: 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 Roam. Nothing to install.

What risk level is append_to_daily_note? +

append_to_daily_note is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit append_to_daily_note? +

Yes. Add a rate_limit block to the append_to_daily_note 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.

How do I block append_to_daily_note completely? +

Set action: deny in the PolicyLayer policy for append_to_daily_note. 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.

What MCP server provides append_to_daily_note? +

append_to_daily_note is provided by the Roam MCP server (@roam-research/roam-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Roam tool call.

Start from Roam, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →