payments_history_list

Get payment history. Returns array of transactions with: id, amount (RUB), type (new_config/renewal/topup/etc.), method (sbp/card/crypto/bonus), days (subscription period purchased), is_paid (completion status), as_key (activation key purchase), created_at (unix seconds).

Server StealthSurf MCP Server stealthsurf-vpn/mcp
Category Read
Risk class Low
Parameters 00 required

What payments_history_list does on StealthSurf MCP Server

AI agents call payments_history_list to retrieve information from StealthSurf MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why payments_history_list needs a policy

Even though payments_history_list only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Questions about payments_history_list

What does the payments_history_list tool do? +

Get payment history. Returns array of transactions with: id, amount (RUB), type (new_config/renewal/topup/etc.), method (sbp/card/crypto/bonus), days (subscription period purchased), is_paid (completion status), as_key (activation key purchase), created_at (unix seconds). It is categorised as a Read tool in the StealthSurf MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on payments_history_list? +

Register the StealthSurf MCP Server MCP server in PolicyLayer and add a rule for payments_history_list: 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 StealthSurf MCP Server. Nothing to install.

What risk level is payments_history_list? +

payments_history_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit payments_history_list? +

Yes. Add a rate_limit block to the payments_history_list 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 payments_history_list completely? +

Set action: deny in the PolicyLayer policy for payments_history_list. 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 payments_history_list? +

payments_history_list is provided by the StealthSurf MCP Server MCP server (stealthsurf-vpn/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.