This record as markdown: /tools/io-github-kivanccakmak-yaver/compiler-version.md
What compiler_version does on Yaver
AI agents call compiler_version to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
compiler | string | Yes | gcc, clang, rustc, go, javac, etc. |
Parameters from the server's own tool schema.
Why compiler_version is rated Low
This tool performs a read-only query to display compiler version metadata. It has no side effects, does not execute code or commands, and does not modify any state. The action is purely informational retrieval, fitting squarely into the Read category with low severity.
From the tool's definition Tool name 'compiler_version' and description 'Show compiler version' indicate a query operation that retrieves version information about compilers without modifying or executing code.
Attacks that exploit this kind of access
The rule that runs compiler_version 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 compiler_version, this is the rule to start with:
compiler_version is read-only, so it stays allowed. 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 compiler_version call is checked against it from then on.
Questions about compiler_version
Show compiler version (gcc, clang, rustc, go, etc.). It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
compiler_version accepts 1 parameter: compiler. Required: compiler. 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 compiler_version: 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.
compiler_version 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 compiler_version 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 compiler_version. 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.
compiler_version 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