dogfood_app_list

List third-party apps enabled for Yaver-account-bound device Dogfood enrollment.

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/dogfood-app-list.md

WHAT IT DOES

What dogfood_app_list does on Yaver

AI agents call dogfood_app_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 dogfood_app_list is rated Low

Tool retrieves configuration state of enrolled device apps without modifying or executing anything.

From the tool's definition List third-party apps enabled for Yaver-account-bound device

Attacks that exploit this kind of access

RECOMMENDED RULE

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

dogfood_app_list Allowed

dogfood_app_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": {
    "dogfood_app_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 dogfood_app_list call is checked against it from then on.

FAQ

Questions about dogfood_app_list

What does the dogfood_app_list tool do? +

List third-party apps enabled for Yaver-account-bound device Dogfood enrollment. 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 dogfood_app_list? +

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

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

Can I rate-limit dogfood_app_list? +

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

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

dogfood_app_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 678 Yaver tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk → The MCP Attack Database →

Guides

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