check_related_forms
AI agents call check_related_forms 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 name and pattern of sibling 'check_*' tools indicate this performs analysis or validation of font glyphs/forms without side effects. No evidence suggests data modification, deletion, or execution of arbitrary code. The empty description reduces confidence below 0.8, but the strong contextual cue from sibling tools and the semantic meaning of 'check' in font design workflows supports classification as Read.
From the tool's definition Tool name 'check_related_forms' with empty description. Semantically, 'check' operations in the context of font analysis tools (per sibling tools like 'check_compatibility', 'check_diagonal_weights', 'check_overshoots') are inspectional/analytical and do not…
Documented attack patterns abuse exactly the kind of access check_related_forms 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_related_forms:
{
"version": "1",
"default": "deny",
"tools": {
"check_related_forms": {}
}
}check_related_forms 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_related_forms. 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_related_forms: 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_related_forms 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_related_forms 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_related_forms. 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_related_forms 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.