This record as markdown: /tools/io-github-kivanccakmak-yaver/prettier-check.md
What prettier_check does on Yaver
AI agents use prettier_check to create or update resources in Yaver, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
check | boolean | — | |
directory | string | — |
Parameters from the server's own tool schema.
Why prettier_check is rated Medium
The tool has two modes: a read-only check mode and a write mode that overwrites source files with reformatted content. Since the tool can modify files (reversibly in the sense that formatting changes can be reverted via version control, but still alters file contents), the most severe applicable category is Write.
From the tool's definition 'Prettier format check or write' — the 'write' mode modifies source files by reformatting them in place.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs prettier_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 prettier_check, this is the rule to start with:
prettier_check stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 prettier_check call is checked against it from then on.
Questions about prettier_check
Prettier format check or write. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
prettier_check accepts 2 parameters: check, 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 prettier_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.
prettier_check is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the prettier_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 prettier_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.
prettier_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.
This server
Across the catalogue