Call this when an AI coding assistant needs to diagnose setup before processing fonts. It checks the font workspace, Node engine compatibility, package versions, cn-font-split runtime details, and WASM availability without writing files, then returns recommendedActions for remediation.
AI agents call get_runtime_status to retrieve information from Mcp Font Split without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
get_runtime_status performs read-only diagnostic queries of system state and environment configuration. It retrieves information about setup status, compatibility, and runtime details without creating, modifying, deleting, or executing any operations. The phrase 'without writing files' further confirms its non-destructive nature. This is a classic diagnostic/monitoring tool that falls squarely into the Read category.
From the tool's definition Tool "checks the font workspace, Node engine compatibility, package versions, cn-font-split runtime details, and WASM availability without writing files" — explicitly stated as diagnostic inspection with no side effects or data modification.
Attacks that exploit this kind of access
Call this when an AI coding assistant needs to diagnose setup before processing fonts. It checks the font workspace, Node engine compatibility, package versions, cn-font-split runtime details, and WASM availability without writing files, then returns recommendedActions for remediation. It is categorised as a Read tool in the Mcp Font Split MCP Server, which means it retrieves data without modifying state.
Register the Mcp Font Split MCP server in PolicyLayer and add a rule for get_runtime_status: 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 Mcp Font Split. Nothing to install.
get_runtime_status 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 get_runtime_status 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 get_runtime_status. 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.
get_runtime_status is provided by the Mcp Font Split MCP server (wenzhimo/mcp-font-split). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →