This record as markdown: /tools/vipcasso-mcp/listcollectionshares.md
What listCollectionShares does on Vipcasso
AI agents call listCollectionShares 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 listCollectionShares is rated Low
Even though listCollectionShares 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)
Attacks that exploit this kind of access
The rule that runs listCollectionShares 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 listCollectionShares, this is the rule to start with:
listCollectionShares 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 listCollectionShares call is checked against it from then on.
Questions about listCollectionShares
GET /v1/collections/{collection_id}/shares. It is categorised as a Read tool in the Vipcasso MCP Server, which means it retrieves data without modifying state.
listCollectionShares 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 listCollectionShares: 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.
listCollectionShares 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 listCollectionShares 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 listCollectionShares. 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.
listCollectionShares 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