This record as markdown: /tools/instantkom-mcp-server/change-password.md
What change_password does on instantKOM MCP Server
AI agents use change_password to create or update resources in instantKOM MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your instantKOM MCP Server environment.
Why change_password is rated Medium
Changing a password is a Write operation (modifies existing account data). However, it carries high severity because an AI agent misusing this tool could lock out legitimate users by changing their passwords, effectively a privilege escalation or account takeover risk.
From the tool's definition 'Change user password' — modifies account credentials
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 instantKOM MCP Server, 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 instantKOM MCP Server, apply this rule, and every change_password call is checked against it from then on.
Questions about change_password
Change user password. It is categorised as a Write tool in the instantKOM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the instantKOM MCP Server 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 instantKOM MCP Server. 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 instantKOM MCP Server MCP server (instantkom/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on instantKOM MCP Server, and thousands of servers like it.
This server
Across the catalogue