dogfood_installation_list

List pending, active, revoked, cancelled, and superseded third-party app installations. Public identity metadata only.

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 10 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-installation-list.md

WHAT IT DOES

What dogfood_installation_list does on Yaver

AI agents call dogfood_installation_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.

Parameter	Type	Required	Description
`appId`	string	—

Parameters from the server's own tool schema.

RISK

Why dogfood_installation_list is rated Low

Tool retrieves installation metadata without modification or side effects; read-only query operation.

From the tool's definition List pending, active, revoked, cancelled, superseded installations. Public identity metadata only.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

dogfood_installation_list Allowed

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

FAQ

Questions about dogfood_installation_list

What does the dogfood_installation_list tool do? +

List pending, active, revoked, cancelled, and superseded third-party app installations. Public identity metadata only. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does dogfood_installation_list accept? +

dogfood_installation_list accepts 1 parameter: appId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on dogfood_installation_list? +

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

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

Can I rate-limit dogfood_installation_list? +

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

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

dogfood_installation_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 →