yaver_help
Answer 'how do I do X with Yaver?' questions. Call this whenever the user wonders what Yaver can do, which feature replaces which SaaS, or how to set something up. Accepts a topic keyword. Topics include: overview, solo-stack (costs + savings summary), forms, newsletter, jobs, image, pdf, oauth, ...
This record as markdown: /tools/io-github-kivanccakmak-yaver/yaver-help.md
What yaver_help does on Yaver
AI agents call yaver_help 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 |
|---|---|---|---|
topic | string | — | Topic keyword (e.g. 'newsletter', 'solo-stack', 'meetings'). Pass empty string for an overview. |
Parameters from the server's own tool schema.
Why yaver_help is rated Low
This tool retrieves documentation/help information based on a topic keyword. It is purely informational with no side effects — it answers questions about Yaver features and capabilities. No data is created, modified, deleted, or executed.
From the tool's definition Answer 'how do I do X with Yaver?' questions...Accepts a topic keyword
Attacks that exploit this kind of access
The rule that runs yaver_help 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 yaver_help, this is the rule to start with:
yaver_help 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 yaver_help call is checked against it from then on.
Questions about yaver_help
Answer 'how do I do X with Yaver?' questions. Call this whenever the user wonders what Yaver can do, which feature replaces which SaaS, or how to set something up. Accepts a topic keyword. Topics include: overview, solo-stack (costs + savings summary), forms, newsletter, jobs, image, pdf, oauth, mail, shortener, waitlist, docs, meetings, wizard, tmux, relay, tunnel, mobile, mcp, runners, tasks, auth. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
yaver_help accepts 1 parameter: topic. 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 yaver_help: 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.
yaver_help 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 yaver_help 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 yaver_help. 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.
yaver_help 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