AI agents call check_junctions 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_*' naming pattern consistently indicates read-only inspection operations in this server. Junctions in typography refer to connection points between strokes that designers review for consistency and quality. No write, execute, destructive, or financial operations are implied.
From the tool's definition Tool name 'check_junctions' suggests an inspection/analysis function. The tool description is empty, preventing direct confirmation.
Documented attack patterns abuse exactly the kind of access check_junctions 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_junctions:
{
"version": "1",
"default": "deny",
"tools": {
"check_junctions": {}
}
}check_junctions 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_junctions. 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_junctions: 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_junctions 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_junctions 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_junctions. 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_junctions 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.