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, ...
AI agents use yaver_help 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 |
|---|---|---|---|
topic | string | — | Topic keyword (e.g. 'newsletter', 'solo-stack', 'meetings'). Pass empty string for an overview. |
Parameters from the server's own tool schema.
An AI agent can call yaver_help faster than any human can review — one bad instruction and it creates or modifies resources in Yaver by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
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 Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
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 Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.