phone_project_templates
List the built-in phone-project templates (blank, crud, todos, notes). Use one of these when calling phone_project_create.
This record as markdown: /tools/io-github-kivanccakmak-yaver/phone-project-templates.md
What phone_project_templates does on Yaver
AI agents call phone_project_templates 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.
Why phone_project_templates is rated Low
This tool only queries and returns a list of available templates. It performs no creation, modification, deletion, or execution of code/commands. The blast radius of misuse is minimal—an agent could only see template names, not cause harm. Categorized as Read due to its informational, non-actionable nature.
From the tool's definition Tool description states 'List the built-in phone-project templates' — a retrieval operation with no side effects. Returns static template options for reference.
Attacks that exploit this kind of access
The rule that runs phone_project_templates 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 phone_project_templates, this is the rule to start with:
phone_project_templates 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 phone_project_templates call is checked against it from then on.
Questions about phone_project_templates
List the built-in phone-project templates (blank, crud, todos, notes). Use one of these when calling phone_project_create. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
Register the Yaver MCP server in PolicyLayer and add a rule for phone_project_templates: 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.
phone_project_templates 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 phone_project_templates 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 phone_project_templates. 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.
phone_project_templates 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