AI agents call remarkable_delete to permanently remove resources in reMarkable MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool name explicitly indicates a delete operation on the reMarkable tablet file system. Delete operations are irreversible and cannot be undone, fitting the Destructive category. High severity due to potential loss of user documents and data on the tablet. High confidence despite empty description because the tool name unambiguously indicates destructive behavior in a file management context.
From the tool's definition Tool name 'remarkable_delete' combined with server context of managing reMarkable tablet files and documents.
Documented attack patterns abuse exactly the kind of access remarkable_delete 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_delete:
{
"version": "1",
"default": "deny",
"hide": [
"remarkable_delete"
]
}remarkable_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
remarkable_delete. It is categorised as a Destructive tool in the reMarkable MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the reMarkable MCP Server MCP server in PolicyLayer and add a rule for remarkable_delete: 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_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remarkable_delete 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_delete. 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_delete 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.