rmx_batch

THE RISK

Low Risk

Why rmx_batch needs a policy

The description is completely empty, providing no information about what this tool does. The name 'rmx_batch' suggests it may be a batch operation (possibly related to the RMX plugin for Glyphs, which handles interpolation/scaling of glyphs), but without a description, the exact action (read, write, execute, destructive) cannot be determined.

From the tool's definition Tool name is 'rmx_batch' and the description is empty or uninformative.

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

POLICY

How to control rmx_batch

PolicyLayer is an MCP gateway — it sits between your AI agents and Glyphs, and nothing reaches the server without passing your rules. This is the rule we recommend for rmx_batch:

policy.json

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

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

Create a free account and register Glyphs — 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 Glyphs tools

Destructive delete_glyph Delete a glyph from the font. This cannot be undone via MCP. Destructive delete_kerning_pair Delete a kerning pair. Execute execute_in_glyphs execute_in_glyphs Execute rmx_scale rmx_scale Write duplicate_glyph Duplicate a glyph (all layers and paths) under a new name. Write create_glyph create_glyph Write rename_glyph Rename a glyph. Fails if new_name already exists. Write set_feature_code Create or update an OpenType feature.

All 41 Glyphs 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 rmx_batch

What does the rmx_batch tool do? +

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

How do I enforce a policy on rmx_batch? +

Register the Glyphs MCP server in PolicyLayer and add a rule for rmx_batch: 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 Glyphs. Nothing to install.

What risk level is rmx_batch? +

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

Can I rate-limit rmx_batch? +

Yes. Add a rate_limit block to the rmx_batch 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 rmx_batch completely? +

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

rmx_batch is provided by the Glyphs MCP server (nmassi/glyphs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Glyphs tool call.

Start from Glyphs, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →