commit_message
Get the current git diff to help generate a conventional commit message.
This record as markdown: /tools/io-github-kivanccakmak-yaver/commit-message.md
What commit_message does on Yaver
AI agents call commit_message 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 |
|---|---|---|---|
directory | string | — |
Parameters from the server's own tool schema.
Why commit_message is rated Low
The tool reads the current git diff to assist in generating a commit message. It does not write, execute, or modify anything; it is a pure read operation. Severity is low because it only exposes source code differences already present in the working directory.
From the tool's definition "Get the current git diff" — retrieves diff data with no side effects
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs commit_message 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 commit_message, this is the rule to start with:
commit_message 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 commit_message call is checked against it from then on.
Questions about commit_message
Get the current git diff to help generate a conventional commit message. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
commit_message accepts 1 parameter: 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 commit_message: 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.
commit_message 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 commit_message 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 commit_message. 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.
commit_message 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