AI agents call list_root to retrieve information from Remark without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a directory listing operation, which is a non-destructive query that retrieves information about the file system structure. It does not modify, delete, or execute anything. The scope is limited to enumeration of the root directory, making it a straightforward Read operation with minimal risk.
From the tool's definition Tool name 'list_root' and description 'List all files and folders in the root of the reMarkable tablet' indicate a retrieval operation with no side effects.
Risk signalsBulk/mass operation — affects multiple targets · Admin/system-level operation
Attacks that exploit this kind of access
List all files and folders in the root of the reMarkable tablet. It is categorised as a Read tool in the Remark MCP Server, which means it retrieves data without modifying state.
Register the Remark MCP server in PolicyLayer and add a rule for list_root: 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 Remark. Nothing to install.
list_root 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 list_root 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 list_root. 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.
list_root is provided by the Remark MCP server (robbogd76/remark-mcp). 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 →