Low Risk

analyze_spacing

analyze_spacing

How to control analyze_spacing ↓

What analyze_spacing does on Glyphs

AI agents call analyze_spacing to retrieve information from Glyphs without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why analyze_spacing needs a policy

The tool name and its placement among other analysis/checking tools strongly suggest it performs read-only inspection of font spacing data rather than modification. The empty description prevents full certainty, but the naming pattern and sibling tools all follow an analysis pattern consistent with Read operations. Even if misused, analyzing spacing poses minimal risk to the font data.

From the tool's definition Tool name 'analyze_spacing' indicates inspection/analysis functionality. Server description emphasizes 'read and write font data' with this tool appearing in an analysis/checking group (analyze_kerning, audit_font_color, check_compatibility, etc.), all…

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

How to control analyze_spacing

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "analyze_spacing": {}
  }
}

analyze_spacing is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Glyphs — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about analyze_spacing

What does the analyze_spacing tool do? +

analyze_spacing. It is categorised as a Read tool in the Glyphs MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on analyze_spacing? +

Register the Glyphs MCP server in PolicyLayer and add a rule for analyze_spacing: 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 analyze_spacing? +

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

Can I rate-limit analyze_spacing? +

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

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

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

Free to start. No card required.

41 Glyphs tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.