dogfood_tester_set

Allow or revoke a Yaver account by email for one app. Revoking also disables that account's pending and active installations.

SERVERYaver SOURCEyaver-cli

Medium RISK CLASS

Category Write

Parameters 33 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-tester-set.md

WHAT IT DOES

What dogfood_tester_set does on Yaver

AI agents use dogfood_tester_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
`appId`	string	Yes
`email`	string	Yes
`enabled`	boolean	Yes

Parameters from the server's own tool schema.

RISK

Why dogfood_tester_set is rated Medium

Modifies account permissions and installation states, affecting service access and deployed instances but reversible via re-enabling.

From the tool's definition Allow or revoke a Yaver account; disables pending and active installations.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

dogfood_tester_set Rate-limited

dogfood_tester_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dogfood_tester_set": {
      "limits": [
        {
          "counter": "dogfood_tester_set_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every dogfood_tester_set call is checked against it from then on.

FAQ

Questions about dogfood_tester_set

What does the dogfood_tester_set tool do? +

Allow or revoke a Yaver account by email for one app. Revoking also disables that account's pending and active installations. 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_tester_set accept? +

dogfood_tester_set accepts 3 parameters: appId, email, enabled. Required: appId, email, enabled. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on dogfood_tester_set? +

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

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

Can I rate-limit dogfood_tester_set? +

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

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

dogfood_tester_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.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 678 Yaver tools →

Across the catalogue

emit_assumption_set on 0sec →set-prioity on Kanban MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →