New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

dogfood_app_set

Create or update a third-party Dogfood app. Defaults to feedback+blackbox; grant builds/reload only with explicit owner intent.

SERVERYaver SOURCEyaver-cli
Medium RISK CLASS
Category Write
Parameters 72 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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

Questions about dogfood_app_set

What does the dogfood_app_set tool do? +

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.

What parameters does dogfood_app_set accept? +

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.

How do I enforce a policy on dogfood_app_set? +

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.

What risk level is dogfood_app_set? +

dogfood_app_set is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit dogfood_app_set? +

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.

How do I block dogfood_app_set completely? +

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.

What MCP server provides dogfood_app_set? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Yaver's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.