change_password
Change the password of the currently authenticated email user. Requires the current password and a new password (min 8 characters).
This record as markdown: /tools/io-github-kivanccakmak-yaver/change-password.md
What change_password does on Yaver
AI agents use change_password 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 |
|---|---|---|---|
new_password | string | Yes | The new password (minimum 8 characters) |
current_password | string | Yes | The current password |
Parameters from the server's own tool schema.
Why change_password is rated Medium
This tool modifies account credentials (password change), which is a Write operation. However, it carries high severity because misuse could lock out the legitimate user or enable account takeover by an attacker. It is reversible in principle (password can be changed again) but requires knowing the current password, so it's Write rather than Destructive.
From the tool's definition Change the password of the currently authenticated email user. Requires the current password and a new password
Attacks that exploit this kind of access
The rule that runs change_password 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 change_password, this is the rule to start with:
change_password 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 change_password call is checked against it from then on.
Questions about change_password
Change the password of the currently authenticated email user. Requires the current password and a new password (min 8 characters). 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.
change_password accepts 2 parameters: new_password, current_password. Required: new_password, current_password. 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 change_password: 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.
change_password 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 change_password 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 change_password. 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.
change_password 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