This record as markdown: /tools/io-github-kivanccakmak-yaver/data-update.md
What data_update does on Yaver
AI agents use data_update 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 |
|---|---|---|---|
id | string | Yes | |
table | string | Yes | |
fields | string | Yes | JSON |
directory | string | — |
Parameters from the server's own tool schema.
Why data_update is rated Medium
The tool updates an existing record, which is a reversible write operation. It modifies data but does not delete or irreversibly destroy it. Severity is medium because an AI agent could overwrite important records if misused, but the operation is scoped to a single record by ID and is theoretically reversible.
From the tool's definition 'Update a record by id' — modifies existing data by identifier
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs data_update 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 data_update, this is the rule to start with:
data_update 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 data_update call is checked against it from then on.
Questions about data_update
Update a record by id. 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.
data_update accepts 4 parameters: id, table, fields, directory. Required: id, table, fields. 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 data_update: 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.
data_update 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 data_update 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 data_update. 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.
data_update 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