yaver_ask

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 51 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What yaver_ask does on Yaver

AI agents call yaver_ask 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
`depth`	string	—	How hard to analyze. 'single' = one read-only agent (fast). 'deep' = a multi-agent graph (investigate → answer → verify) for broad/architectural questions. 'aut
`model`	string	—	Model id forwarded to the runner. Empty = runner default.
`runner`	string	—	Runner ID — claude / codex / opencode. Empty = agent default.
`question`	string	Yes	The natural-language question to answer against this repo / machine.
`work_dir`	string	—	Optional project directory to scope the analysis to. Empty = the agent's default workdir / auto-detected from the question.

Parameters from the server's own tool schema.

RISK

Why yaver_ask is rated Low

This tool is fundamentally a code analysis and question-answering tool. It retrieves and inspects repository contents to provide grounded answers, which is a Read operation. The phrase 'it only modifies the working tree / deploys' suggests modifications are not the intent; the tool prioritizes explanation over action.

From the tool's definition Tool description explicitly states it 'reads the actual code (greps, opens files, follows the wiring)' and 'only modifies the working tree / deploys' if needed—but the primary stated purpose is asking questions and getting answers with citations, not making…

Attacks that exploit this kind of access

RECOMMENDED RULE

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

yaver_ask Allowed

yaver_ask 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": {
    "yaver_ask": {}
  }
}

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 yaver_ask call is checked against it from then on.

FAQ

Questions about yaver_ask

What does the yaver_ask tool do? +

Ask a natural-language QUESTION about this repository / machine and get a deep, grounded answer instead of just running work. Use this for 'how do I test STT/TTS?', 'where does auth get wired?', 'why does the relay fall back?' — anything where the user wants understanding, not a change. It spawns a coding agent that reads the actual code (greps, opens files, follows the wiring), answers with file:line citations, automatically escalates from a shallow scan to a wider cross-checked read when the question is broad or architectural, and explains FIRST — it only modifies the working tree / deploys / touches git after confirming with the user via yaver_ask_user. Returns a task object; stream it with the task's /output SSE or poll get_task for the answer. Prefer this over create_task whenever the intent is to explain rather than to build. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does yaver_ask accept? +

yaver_ask accepts 5 parameters: depth, model, runner, question, work_dir. Required: question. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on yaver_ask? +

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

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

Can I rate-limit yaver_ask? +

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

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

yaver_ask 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

ask_about_cocktail on Cocktails RAG MCP Server → The MCP Attack Database →

Guides

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