edit_note · Pulse Workflow MCP Server MCP: Risk & Policy

WHAT IT DOES

What edit_note does on Pulse Workflow MCP Server

AI agents use edit_note to create or update resources in Pulse Workflow MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pulse Workflow MCP Server environment.

WHY IT NEEDS A POLICY

Why edit_note needs a policy

This tool modifies data (sticky notes in a Pulse workflow) but does not delete or irreversibly destroy information, nor does it execute arbitrary code or move money. It's a Write operation because it creates or modifies data reversibly. Severity is medium because misuse could corrupt workflow documentation or mislead collaborators, but the blast radius is limited to note content within a single workflow context.

From the tool's definition Tool name 'edit_note' and description 'Update sticky note' indicate modification of existing data (sticky notes). The action is reversible—notes can be edited again or reverted.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

edit_note Rate-limited

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

View as policy code

policy.json

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Pulse Workflow MCP Server, so you can run agents against it safely.

FAQ

Questions about edit_note

What does the edit_note tool do? +

Update sticky note. It is categorised as a Write tool in the Pulse Workflow MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on edit_note? +

Register the Pulse Workflow MCP Server MCP server in PolicyLayer and add a rule for edit_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 Pulse Workflow MCP Server. Nothing to install.

What risk level is edit_note? +

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

Can I rate-limit edit_note? +

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

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

edit_note is provided by the Pulse Workflow MCP Server MCP server (pulse-intelligence/pulse-workflow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.