dunning_configure
Update dunning (payment recovery) configuration for an organization. All fields except organizationSlug are optional — only provided fields are updated, rest stays unchanged.
This record as markdown: /tools/com-servicialo-mcp-server/dunning-configure.md
What dunning_configure does on Servicialo
AI agents use dunning_configure to create or update resources in Servicialo, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Servicialo environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
steps | array | — | |
enabled | boolean | — | |
blockOnStep5 | boolean | — | |
gracePeriodDays | integer | — | |
organizationSlug | string | Yes |
Parameters from the server's own tool schema.
Why dunning_configure is rated Medium
This tool modifies payment recovery configuration, which affects how an organization's financial operations function. While it is reversible (configuration can be updated again), it directly controls payment collection mechanisms and could impact billing workflows, customer payment reminders, and financial processes if misconfigured by an AI agent.
From the tool's definition Tool name 'dunning_configure' and description explicitly states 'Update dunning (payment recovery) configuration for an organization.' The verb 'Update' and the financial domain context (dunning = payment recovery process) indicate modification of financial…
Attacks that exploit this kind of access
The rule that runs dunning_configure 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 dunning_configure, this is the rule to start with:
dunning_configure stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 dunning_configure call is checked against it from then on.
Questions about dunning_configure
Update dunning (payment recovery) configuration for an organization. All fields except organizationSlug are optional — only provided fields are updated, rest stays unchanged. It is categorised as a Write tool in the Servicialo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
dunning_configure accepts 5 parameters: steps, enabled, blockOnStep5, gracePeriodDays, organizationSlug. Required: organizationSlug. 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 dunning_configure: 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.
dunning_configure is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the dunning_configure 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 dunning_configure. 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.
dunning_configure 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