This record as markdown: /tools/io-github-kivanccakmak-yaver/template-use.md
What template_use does on Yaver
AI agents use template_use 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 |
|---|---|---|---|
name | string | Yes | Template name |
project_name | string | — | Project name |
Parameters from the server's own tool schema.
Why template_use is rated Medium
The tool creates new data structures (a full-stack project) in a reversible manner. This is a Write operation—it produces new files and configuration but does not execute arbitrary code, delete data, or commit financial transactions. Severity is medium because misuse could result in resource consumption or unwanted project creation, but the effects are recoverable by deletion.
From the tool's definition Tool name 'template_use' combined with description 'Apply a full-stack template to create a new project' indicates creation of new project artifacts.
Attacks that exploit this kind of access
The rule that runs template_use 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 template_use, this is the rule to start with:
template_use 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 template_use call is checked against it from then on.
Questions about template_use
Apply a full-stack template to create a new project. 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.
template_use accepts 2 parameters: name, project_name. Required: name. 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 template_use: 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.
template_use 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 template_use 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 template_use. 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.
template_use 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