license

Generate a license file (MIT, Apache, GPL).

SERVERYaver SOURCEyaver-cli

Medium RISK CLASS

Category Write

Parameters 31 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/license.md

WHAT IT DOES

What license does on Yaver

AI agents use license 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
`type`	string	Yes	mit, apache, gpl
`year`	integer	—
`author`	string	—

Parameters from the server's own tool schema.

RISK

Why license is rated Medium

The tool creates a new file (a license file) in the project. This is a reversible write operation — the file can be deleted or overwritten. No code is executed, no data is destroyed, and no financial transaction occurs. Blast radius is low since it only creates a standard license text file.

From the tool's definition Generate a license file (MIT, Apache, GPL)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs license 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 license, this is the rule to start with:

license Rate-limited

license 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "license": {
      "limits": [
        {
          "counter": "license_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every license call is checked against it from then on.

FAQ

Questions about license

What does the license tool do? +

Generate a license file (MIT, Apache, GPL). 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.

What parameters does license accept? +

license accepts 3 parameters: type, year, author. Required: type. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on license? +

Register the Yaver MCP server in PolicyLayer and add a rule for license: 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.

What risk level is license? +

license is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit license? +

Yes. Add a rate_limit block to the license 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.

How do I block license completely? +

Set action: deny in the PolicyLayer policy for license. 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.

What MCP server provides license? +

license 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.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →