template_list

List available project templates (saas-complete, indie-hacker, api-first, content-site, survey-app).

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What template_list does on Yaver

AI agents call template_list 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.

RISK

Why template_list is rated Low

This tool retrieves and enumerates project templates available on a local development system. While the retrieval itself is low-impact (read-only), the context is critical: Yaver is a phone-first local development platform that handles deployment pipelines ('run, build, deploy').

From the tool's definition Lists available project templates from the Yaver development server. The description explicitly states it 'List[s] available project templates' with specific template names (saas-complete, indie-hacker, api-first, content-site, survey-app).

Attacks that exploit this kind of access

RECOMMENDED RULE

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

template_list Allowed

template_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "template_list": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about template_list

What does the template_list tool do? +

List available project templates (saas-complete, indie-hacker, api-first, content-site, survey-app). It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on template_list? +

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

template_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit template_list? +

Yes. Add a rate_limit block to the template_list 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 template_list completely? +

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

template_list 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

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →