feedback_create

Mint a FeedbackReport programmatically. Optional screenshotSessionId auto-attaches a runtime_frame JPEG. surface must be one of phone/tablet/watch/tv/vision/car/web/feedback-sdk.

SERVERYaver SOURCEyaver-cli

Medium RISK CLASS

Category Write

Parameters 101 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/feedback-create.md

WHAT IT DOES

What feedback_create does on Yaver

AI agents use feedback_create 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
`model`	string	—
`source`	string	—	yaver-app \| in-app-sdk \| mcp (default mcp).
`appName`	string	—
`buildId`	string	—
`surface`	string	Yes
`platform`	string	—
`osVersion`	string	—
`appVersion`	string	—
`transcript`	string	—	What the reporter said or the runner captured.
`screenshotSessionId`	string	—	Optional runtime session — its current /frame becomes the report screenshot.

Parameters from the server's own tool schema.

RISK

Why feedback_create is rated Medium

This tool creates feedback report records with optional metadata (screenshots, surface type). It is a reversible write operation that generates new data without deleting or modifying existing records, executing arbitrary code, or moving financial resources. The blast radius is minimal—even if misused, it only creates feedback entries which are generally low-risk logs or telemetry data.

From the tool's definition The tool description explicitly uses the verb 'Mint' and 'programmatically' create a FeedbackReport, with optional parameters for attaching screenshots and specifying surface types. This is a create operation that generates new data records.

Risk signalsHigh parameter count (10 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

feedback_create Rate-limited

feedback_create 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": {
    "feedback_create": {
      "limits": [
        {
          "counter": "feedback_create_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 feedback_create call is checked against it from then on.

FAQ

Questions about feedback_create

What does the feedback_create tool do? +

Mint a FeedbackReport programmatically. Optional screenshotSessionId auto-attaches a runtime_frame JPEG. surface must be one of phone/tablet/watch/tv/vision/car/web/feedback-sdk. 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 feedback_create accept? +

feedback_create accepts 10 parameters: model, source, appName, buildId, surface, platform, osVersion, appVersion, transcript, screenshotSessionId. Required: surface. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on feedback_create? +

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

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

Can I rate-limit feedback_create? +

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

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

feedback_create 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 645 Yaver tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

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