grantPlatformTestCredits
Adds credits for tests to any account. They are shown on the account's statement as "Test credits from Vipcasso", are spent after the plan allowance and before bought credits, and are never counted as revenue. At most 10000 per grant and 25000 unspent per account. A reason is required; an expiry ...
This record as markdown: /tools/vipcasso-mcp/grantplatformtestcredits.md
What grantPlatformTestCredits does on Vipcasso
AI agents call grantPlatformTestCredits 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
body | object | — | |
files | array | — | |
query | object | — | |
fields | object | — | |
path_params | object | — |
Parameters from the server's own tool schema.
Why grantPlatformTestCredits is rated Low
Even though grantPlatformTestCredits 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) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs grantPlatformTestCredits safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vipcasso, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For grantPlatformTestCredits, this is the rule to start with:
grantPlatformTestCredits 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 Vipcasso, apply this rule, and every grantPlatformTestCredits call is checked against it from then on.
Questions about grantPlatformTestCredits
Adds credits for tests to any account. They are shown on the account's statement as "Test credits from Vipcasso", are spent after the plan allowance and before bought credits, and are never counted as revenue. At most 10000 per grant and 25000 unspent per account. A reason is required; an expiry is optional. Every grant is audited. Requires an Idempotency-Key: one grant per key per account, durably (a retry never adds credits twice). Anyone but the platform gets 404. It is categorised as a Read tool in the Vipcasso MCP Server, which means it retrieves data without modifying state.
grantPlatformTestCredits accepts 5 parameters: body, files, query, fields, path_params. The full parameter table on this page comes from the server's own tool schema.
Register the Vipcasso MCP server in PolicyLayer and add a rule for grantPlatformTestCredits: 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.
grantPlatformTestCredits 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 grantPlatformTestCredits 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 grantPlatformTestCredits. 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.
grantPlatformTestCredits 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.
This server
Across the catalogue