Critical Risk →

delete_daily_note

Delete a specific daily note by date

How to control delete_daily_note ↓

What delete_daily_note does on GistPad MCP

AI agents call delete_daily_note to permanently remove resources in GistPad MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why delete_daily_note needs a policy

Deletion is an irreversible operation that removes data permanently. Even though daily notes are typically user-owned personal data (not critical infrastructure), the loss of unrecoverable personal knowledge, documentation, or decision records poses a significant risk if an AI agent misuses this tool without explicit user intent. The high severity reflects the potential for unintended data loss.

From the tool's definition Tool name is 'delete_daily_note' and description explicitly states 'Delete a specific daily note by date'. The verb 'delete' combined with the irreversible nature of removing a note from the system.

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

How to control delete_daily_note

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

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_daily_note"
  ]
}

delete_daily_note disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register GistPad MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_daily_note

What does the delete_daily_note tool do? +

Delete a specific daily note by date. It is categorised as a Destructive tool in the GistPad MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_daily_note? +

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

What risk level is delete_daily_note? +

delete_daily_note is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_daily_note? +

Yes. Add a rate_limit block to the delete_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 delete_daily_note completely? +

Set action: deny in the PolicyLayer policy for delete_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 delete_daily_note? +

delete_daily_note is provided by the GistPad MCP server (lostintangent/gistpad-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every GistPad MCP tool call.

Start from GistPad MCP, 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.

23 GistPad MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.