add_memo_by_anchor

find_text가 반환한 anchor로 메모 위치를 지정해 메모를 추가합니다.

SERVERHwpx SOURCEairmang/hwpx-mcp-server

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/airmang-hwpx-mcp-server/add-memo-by-anchor.md

WHAT IT DOES

What add_memo_by_anchor does on Hwpx

AI agents use add_memo_by_anchor to create or update resources in Hwpx, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hwpx environment.

RISK

Why add_memo_by_anchor is rated Medium

This tool creates new data (a memo) within a document in a reversible manner. It does not delete, execute arbitrary code, or move money. The moderate severity reflects that adding memos could be misused to inject misleading annotations into documents, but the operation is reversible via standard undo/deletion mechanisms.

From the tool's definition Tool name 'add_memo_by_anchor' and description indicate it adds/inserts a memo into a document at a specified anchor position.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs add_memo_by_anchor safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Hwpx, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_memo_by_anchor, this is the rule to start with:

add_memo_by_anchor Rate-limited

add_memo_by_anchor 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": {
    "add_memo_by_anchor": {
      "limits": [
        {
          "counter": "add_memo_by_anchor_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Hwpx, apply this rule, and every add_memo_by_anchor call is checked against it from then on.

FAQ

Questions about add_memo_by_anchor

What does the add_memo_by_anchor tool do? +

find_text가 반환한 anchor로 메모 위치를 지정해 메모를 추가합니다. It is categorised as a Write tool in the Hwpx MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_memo_by_anchor? +

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

What risk level is add_memo_by_anchor? +

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

Can I rate-limit add_memo_by_anchor? +

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

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

add_memo_by_anchor is provided by the Hwpx MCP server (airmang/hwpx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Hwpx, and thousands of servers like it.

This server

All 109 Hwpx tools →

Across the catalogue

add-tag on Kanban MCP Server →kb_add on Persistent Kb → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →