list_payment_methods
List the signed-in user's saved payment cards (brand, last 4, expiry, default). Use the returned publicId with create_one_click_checkout to pre-select a card.
This record as markdown: /tools/com-getmyhotels-getmyhotels/list-payment-methods.md
What list_payment_methods does on GetMyHotels
AI agents call list_payment_methods to retrieve information from GetMyHotels without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_payment_methods is rated Low
This tool retrieves and displays stored payment card information without creating charges, modifying data, or executing transactions. However, severity is elevated from low to medium because payment card metadata (brand, last 4 digits, expiry) is sensitive PII that could be misused if an agent were compromised or manipulated into exfiltrating or logging this information.
From the tool's definition Tool 'lists' payment methods and 'returns' card metadata (brand, last 4, expiry, default). Description emphasizes retrieval: 'List the signed-in user's saved payment cards' with no modification, deletion, or financial transaction.
Attacks that exploit this kind of access
The rule that runs list_payment_methods safely
PolicyLayer is an MCP gateway: it sits between your AI agents and GetMyHotels, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_payment_methods, this is the rule to start with:
list_payment_methods is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GetMyHotels, apply this rule, and every list_payment_methods call is checked against it from then on.
Questions about list_payment_methods
List the signed-in user's saved payment cards (brand, last 4, expiry, default). Use the returned publicId with create_one_click_checkout to pre-select a card. It is categorised as a Read tool in the GetMyHotels MCP Server, which means it retrieves data without modifying state.
Register the GetMyHotels MCP server in PolicyLayer and add a rule for list_payment_methods: 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 GetMyHotels. Nothing to install.
list_payment_methods is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_payment_methods 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 list_payment_methods. 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.
list_payment_methods is provided by the GetMyHotels MCP server (https://mcp.getmyhotels.com). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GetMyHotels, and thousands of servers like it.
This server
Across the catalogue