AI agents use remarkable_rename to create or update resources in reMarkable MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your reMarkable MCP Server environment.
Renaming files is a write operation that modifies metadata reversibly. It's less severe than deletion (remarkable_delete) but more than read operations. Severity is medium because renaming could cause confusion or data organization issues, but the operation is undoable via another rename call.
From the tool's definition Tool name 'remarkable_rename' indicates it renames files/documents on the reMarkable tablet. The description is empty, but renaming is a reversible modification operation.
Documented attack patterns abuse exactly the kind of access remarkable_rename gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and reMarkable MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for remarkable_rename:
{
"version": "1",
"default": "deny",
"tools": {
"remarkable_rename": {
"limits": [
{
"counter": "remarkable_rename_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}remarkable_rename 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.
remarkable_rename. It is categorised as a Write tool in the reMarkable MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the reMarkable MCP Server MCP server in PolicyLayer and add a rule for remarkable_rename: 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 reMarkable MCP Server. Nothing to install.
remarkable_rename 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 remarkable_rename 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 remarkable_rename. 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.
remarkable_rename is provided by the reMarkable MCP Server MCP server (pypi:remarkable-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from reMarkable 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.
14 reMarkable MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.