check_diagonal_weights
AI agents call check_diagonal_weights 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.
The 'check_' prefix pattern on this server indicates diagnostic/analytical operations that read font data without modification. While the description is uninformative, the consistent naming convention across sibling audit tools and the lack of modification language (no 'update', 'set', 'modify') strongly suggests this reads or analyzes diagonal weight properties in font glyphs.
From the tool's definition Tool name 'check_diagonal_weights' suggests an analysis/inspection operation. Prefix 'check_' across sibling tools (check_compatibility, check_junctions, check_overshoots, check_punctuation) consistently indicates read-only audit functions.
Documented attack patterns abuse exactly the kind of access check_diagonal_weights gives an agent:
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 check_diagonal_weights:
{
"version": "1",
"default": "deny",
"tools": {
"check_diagonal_weights": {}
}
}check_diagonal_weights 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.
check_diagonal_weights. It is categorised as a Read tool in the Glyphs MCP Server, which means it retrieves data without modifying state.
Register the Glyphs MCP server in PolicyLayer and add a rule for check_diagonal_weights: 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.
check_diagonal_weights 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 check_diagonal_weights 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 check_diagonal_weights. 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.
check_diagonal_weights 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.
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.