my_tool

THE RISK

Low Risk

Why my_tool needs a policy

With no description and only a generic name, it is impossible to determine the tool's function. Given the server context (reMarkable tablet access), it could be anything, but without evidence, I default to Other with very low confidence.

From the tool's definition Tool name 'my_tool' is generic and the description is empty, providing no information about what the tool does.

Documented attack patterns abuse exactly the kind of access my_tool gives an agent:

POLICY

How to control my_tool

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 my_tool:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "my_tool": {
      "limits": [
        {
          "counter": "my_tool_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

my_tool gets a rate cap, and everything else on the server is denied unless you say otherwise.

Create a free account and register reMarkable MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

SET A RULE FOR THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More reMarkable MCP Server tools

Destructive remarkable_delete remarkable_delete Write remarkable_mkdir remarkable_mkdir Write remarkable_move remarkable_move Write remarkable_rename remarkable_rename Write remarkable_upload remarkable_upload Read my_ocr_tool my_ocr_tool Read remarkable_browse remarkable_browse Read remarkable_canvas remarkable_canvas

All 14 reMarkable MCP Server tools →

Other tools on other servers

Android Forensics ADB MCP Server generate_app_analysis_report Ethereum Tools add Math MCP Server complex_analysis_suite Crypto_MCP aes_encrypt

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Tool risk categories → How PolicyLayer classifies MCP tools by what they can do.
MCP tool → What an MCP tool is and how clients discover and call it.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about my_tool

What does the my_tool tool do? +

my_tool. It is categorised as a Other tool in the reMarkable MCP Server MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on my_tool? +

Register the reMarkable MCP Server MCP server in PolicyLayer and add a rule for my_tool: 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.

What risk level is my_tool? +

my_tool is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit my_tool? +

Yes. Add a rate_limit block to the my_tool 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.

How do I block my_tool completely? +

Set action: deny in the PolicyLayer policy for my_tool. 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.

What MCP server provides my_tool? +

my_tool 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.

Enforce policy on every reMarkable MCP Server tool call.

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.

CHECK YOUR STACK →