This record as markdown: /tools/io-github-kivanccakmak-yaver/type-check.md
What type_check does on Yaver
AI agents invoke type_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 |
|---|---|---|---|
tool | string | — | Custom type check command (auto-detected if empty) |
directory | string | — | Project directory |
Parameters from the server's own tool schema.
Why type_check is rated High
This tool executes external processes (tsc, go build, mypy, pyright) on the local system. While type checking is generally read-only in intent, it actively runs build tools and compilers, which qualifies as Execute. Misuse risk is medium — it triggers real processes but is unlikely to cause data loss or financial harm.
From the tool's definition Run type checker. Auto-detects: tsc, go build, mypy/pyright.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs type_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 type_check, this is the rule to start with:
type_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 type_check call is checked against it from then on.
Questions about type_check
Run type checker. Auto-detects: tsc, go build, mypy/pyright. 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.
type_check accepts 2 parameters: tool, 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 type_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.
type_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 type_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 type_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.
type_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