New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

getPaymentAccount

GET /v1/payments/account

SERVERVipcasso SOURCE@vipcasso/mcp
Low RISK CLASS
Category Read
Parameters 50 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/vipcasso-mcp/getpaymentaccount.md

What getPaymentAccount does on Vipcasso

AI agents call getPaymentAccount to retrieve information from Vipcasso without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
body object —
files array —
query object —
fields object —
path_params object —

Parameters from the server's own tool schema.

Why getPaymentAccount is rated Low

Even though getPaymentAccount 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.

Risk signalsAccepts file system path (files[].filename) · Accepts raw HTML/template content (body)

Questions about getPaymentAccount

What does the getPaymentAccount tool do? +

GET /v1/payments/account. It is categorised as a Read tool in the Vipcasso MCP Server, which means it retrieves data without modifying state.

What parameters does getPaymentAccount accept? +

getPaymentAccount accepts 5 parameters: body, files, query, fields, path_params. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on getPaymentAccount? +

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

What risk level is getPaymentAccount? +

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

Can I rate-limit getPaymentAccount? +

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

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

getPaymentAccount is provided by the Vipcasso MCP server (@vipcasso/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Vipcasso, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Vipcasso's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.