dogfood_installation_action
Approve a key-verified pending installation, cancel a pending enrollment, or revoke an active installation. Re-registration approval supersedes the prior key generation for the same slot.
This record as markdown: /tools/io-github-kivanccakmak-yaver/dogfood-installation-action.md
What dogfood_installation_action does on Yaver
AI agents call dogfood_installation_action to permanently remove resources in Yaver, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
action | string | Yes | |
installationId | string | Yes | Backend installation document id from dogfood_installation_list. |
Parameters from the server's own tool schema.
Why dogfood_installation_action is rated Critical
Revoking or cancelling installations are irreversible actions with significant blast radius.
From the tool's definition cancel a pending enrollment, or revoke an active installation
Attacks that exploit this kind of access
The rule that runs dogfood_installation_action 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_action, this is the rule to start with:
dogfood_installation_action is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every dogfood_installation_action call is checked against it from then on.
Questions about dogfood_installation_action
Approve a key-verified pending installation, cancel a pending enrollment, or revoke an active installation. Re-registration approval supersedes the prior key generation for the same slot. It is categorised as a Destructive tool in the Yaver MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
dogfood_installation_action accepts 2 parameters: action, installationId. Required: action, installationId. 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 dogfood_installation_action: 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.
dogfood_installation_action is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the dogfood_installation_action 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 dogfood_installation_action. 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.
dogfood_installation_action 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.
Across the catalogue