disputes_list
List disputes for an organization. Filter by status or type. Returns disputes with client and provider info.
This record as markdown: /tools/com-servicialo-mcp-server/disputes-list.md
What disputes_list does on Servicialo
AI agents call disputes_list to retrieve information from Servicialo 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 |
|---|---|---|---|
page | integer | — | |
type | string | — | |
limit | integer | — | |
apiKey | string | — | |
status | string | — | |
orgSlug | string | Yes |
Parameters from the server's own tool schema.
Why disputes_list is rated Low
This tool performs a retrieval operation on dispute records with optional filtering. It has no side effects, does not modify, delete, or execute any operations. The blast radius of misuse is minimal—an agent could over-retrieve disputes data or filter inappropriately, but cannot create, modify, or delete disputes. This is a straightforward Read category tool.
From the tool's definition Tool name 'disputes_list' and description 'List disputes for an organization. Filter by status or type. Returns disputes with client and provider info.' indicate a read-only query operation that retrieves and filters existing dispute data without modifying…
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs disputes_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Servicialo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For disputes_list, this is the rule to start with:
disputes_list 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 Servicialo, apply this rule, and every disputes_list call is checked against it from then on.
Questions about disputes_list
List disputes for an organization. Filter by status or type. Returns disputes with client and provider info. It is categorised as a Read tool in the Servicialo MCP Server, which means it retrieves data without modifying state.
disputes_list accepts 6 parameters: page, type, limit, apiKey, status, orgSlug. Required: orgSlug. The full parameter table on this page comes from the server's own tool schema.
Register the Servicialo MCP server in PolicyLayer and add a rule for disputes_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 Servicialo. Nothing to install.
disputes_list 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 disputes_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.
Set action: deny in the PolicyLayer policy for disputes_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.
disputes_list is provided by the Servicialo MCP server (@servicialo/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Servicialo, and thousands of servers like it.
This server
Across the catalogue