AI agents use remove_note_from_topic to create or update resources in GetNote MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GetNote MCP Server environment.
This tool removes a note from a topic/knowledge base, which is a reversible organizational action (the note itself is not deleted, just disassociated from the topic). This is a Write-level operation — it modifies the association between a note and a knowledge base, but does not permanently destroy data. It is less severe than 'delete_note' which would be Destructive.
From the tool's definition 将笔记从知识库中移除 (Remove a note from a knowledge base)
Documented attack patterns abuse exactly the kind of access remove_note_from_topic gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GetNote MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_note_from_topic:
{
"version": "1",
"default": "deny",
"tools": {
"remove_note_from_topic": {
"limits": [
{
"counter": "remove_note_from_topic_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}remove_note_from_topic 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.
Free to start. No card required.
将笔记从知识库中移除。. It is categorised as a Write tool in the GetNote MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GetNote MCP Server MCP server in PolicyLayer and add a rule for remove_note_from_topic: 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 GetNote MCP Server. Nothing to install.
remove_note_from_topic 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 remove_note_from_topic 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 remove_note_from_topic. 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.
remove_note_from_topic is provided by the GetNote MCP Server MCP server (iswalle/getnote-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from GetNote MCP Server, 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.
26 GetNote MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.