CHANGE_PASSWORD · Travel Agent MCP Server MCP: Risk & Policy

WHAT IT DOES

What CHANGE_PASSWORD does on Travel Agent MCP Server

AI agents use CHANGE_PASSWORD to create or update resources in Travel Agent MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Travel Agent MCP Server environment.

WHY IT NEEDS A POLICY

Why CHANGE_PASSWORD needs a policy

Changing a password is a Write operation that modifies account credentials. It is high severity because an AI agent misusing this tool could lock a user out of their account or enable unauthorized access by setting an unknown password. Confidence is slightly reduced because the description is truncated and may imply broader account-level changes, but the most likely interpretation remains a password change.

From the tool's definition Tool name 'CHANGE_PASSWORD' and partial description 'Change the logged-in user' (description appears truncated/incomplete)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

CHANGE_PASSWORD Rate-limited

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.

View as policy code

policy.json

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Travel Agent MCP Server, so you can run agents against it safely.

FAQ

Questions about CHANGE_PASSWORD

What does the CHANGE_PASSWORD tool do? +

Change the logged-in user. It is categorised as a Write tool in the Travel Agent MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on CHANGE_PASSWORD? +

Register the Travel Agent 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 Travel Agent MCP Server. Nothing to install.

What risk level is CHANGE_PASSWORD? +

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

Can I rate-limit CHANGE_PASSWORD? +

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.

How do I block CHANGE_PASSWORD completely? +

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.

What MCP server provides CHANGE_PASSWORD? +

CHANGE_PASSWORD is provided by the Travel Agent MCP Server MCP server (nxgnosis/travelagentmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.