Rename a document or change its parent folder.
AI agents use refmd-update-document to create or update resources in RefMD MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RefMD MCP Server environment.
This tool modifies document properties (name, location) without destroying data or executing code. Changes are reversible through subsequent updates, making it a Write category action. Severity is medium because renaming/relocating documents could cause confusion or break references if done carelessly by an agent, but the impact is localized to metadata and organizational state, not data loss or financial harm.
From the tool's definition Tool description explicitly states 'Rename a document or change its parent folder' — these are reversible modifications to document metadata and organizational structure.
Attacks that exploit this kind of access
Rename a document or change its parent folder. It is categorised as a Write tool in the RefMD MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RefMD MCP Server MCP server in PolicyLayer and add a rule for refmd-update-document: 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 RefMD MCP Server. Nothing to install.
refmd-update-document 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 refmd-update-document 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 refmd-update-document. 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.
refmd-update-document is provided by the RefMD MCP Server MCP server (refmdio/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →