AI agents call remarkable_recent to retrieve information from reMarkable MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite empty tool description, the naming convention ('remarkable_recent') and context strongly suggest this retrieves recent documents or files from the tablet—a read-only query operation with no side effects. The sibling tools like 'remarkable_read', 'remarkable_browse', and 'remarkable_image' confirm the server's read-focused purpose.
From the tool's definition Tool named 'remarkable_recent' on a reMarkable tablet access server with sibling tools indicating file browsing and reading operations. The server description emphasizes 'read documents, browse files, extract text' as primary functions.
Documented attack patterns abuse exactly the kind of access remarkable_recent 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_recent:
{
"version": "1",
"default": "deny",
"tools": {
"remarkable_recent": {}
}
}remarkable_recent is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
remarkable_recent. It is categorised as a Read tool in the reMarkable MCP Server MCP Server, which means it retrieves data without modifying state.
Register the reMarkable MCP Server MCP server in PolicyLayer and add a rule for remarkable_recent: 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_recent is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the remarkable_recent 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_recent. 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_recent 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.