dogfood_app_set
Create or update a third-party Dogfood app. Defaults to feedback+blackbox; grant builds/reload only with explicit owner intent.
This record as markdown: /tools/io-github-kivanccakmak-yaver/dogfood-app-set.md
What dogfood_app_set does on Yaver
AI agents use dogfood_app_set 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 |
|---|---|---|---|
appId | string | Yes | |
label | string | Yes | |
enabled | boolean | — | |
projectSlug | string | — | |
activationUrl | string | — | Public SDK activation URL. Must match the appId-derived yaver-dogfood scheme. |
allowedScopes | array | — | |
targetDeviceId | string | — |
Parameters from the server's own tool schema.
Why dogfood_app_set is rated Medium
Creates or modifies app configuration with access controls; reversible action with scope limitations via explicit intent requirements.
From the tool's definition Create or update a third-party Dogfood app, defaults to feedback+blackbox
Attacks that exploit this kind of access
The rule that runs dogfood_app_set 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_set, this is the rule to start with:
dogfood_app_set stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every dogfood_app_set call is checked against it from then on.
Questions about dogfood_app_set
Create or update a third-party Dogfood app. Defaults to feedback+blackbox; grant builds/reload only with explicit owner intent. 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.
dogfood_app_set accepts 7 parameters: appId, label, enabled, projectSlug, activationUrl, allowedScopes, targetDeviceId. Required: appId, label. 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_app_set: 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_app_set 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 dogfood_app_set 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_app_set. 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_app_set 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.
This server
Across the catalogue