This record as markdown: /tools/io-github-kivanccakmak-yaver/tsc-check.md
What tsc_check does on Yaver
AI agents invoke tsc_check to trigger actions in Yaver. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
no_emit | boolean | — | |
directory | string | — |
Parameters from the server's own tool schema.
Why tsc_check is rated High
Running tsc invokes an external compiler/toolchain process. While it is read-only with respect to source files (it doesn't modify them), it executes an external program whose behavior depends on the project configuration and arguments. This places it in the Execute category. Severity is medium because a misconfigured or malicious tsconfig could cause unintended side effects, but in normal use it is relatively safe.
From the tool's definition TypeScript type checking — runs the TypeScript compiler (tsc) as an external process to analyze code
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs tsc_check safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tsc_check, this is the rule to start with:
tsc_check stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every tsc_check call is checked against it from then on.
Questions about tsc_check
TypeScript type checking. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
tsc_check accepts 2 parameters: no_emit, directory. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for tsc_check: 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 Yaver. Nothing to install.
tsc_check is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the tsc_check 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 tsc_check. 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.
tsc_check is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
Across the catalogue