treatment_plans_list
List treatment/care plans of an organization with client, provider, status, objectives and their items (services with quantity/frequency/priority). Filter by clientId, status or proveedorId; paginated (page/limit). Read-only — plan creation/editing stays in the UI (requires clinical supervision).
This record as markdown: /tools/com-servicialo-mcp-server/treatment-plans-list.md
What treatment_plans_list does on Servicialo
AI agents call treatment_plans_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 | — | |
limit | integer | — | |
apiKey | string | — | |
status | string | — | |
orgSlug | string | Yes | |
clientId | string | — | |
proveedorId | string | — |
Parameters from the server's own tool schema.
Why treatment_plans_list is rated Low
This tool retrieves and queries existing treatment/care plan data with filtering and pagination. It performs no side effects, does not modify data, and explicitly documents that it is read-only. The output is informational data about healthcare plans (client, provider, status, objectives).
From the tool's definition Tool description explicitly states 'List treatment/care plans' and 'Read-only — plan creation/editing stays in the UI'. The verb is 'list' with filtering and pagination parameters typical of query operations.
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs treatment_plans_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 treatment_plans_list, this is the rule to start with:
treatment_plans_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 treatment_plans_list call is checked against it from then on.
Questions about treatment_plans_list
List treatment/care plans of an organization with client, provider, status, objectives and their items (services with quantity/frequency/priority). Filter by clientId, status or proveedorId; paginated (page/limit). Read-only — plan creation/editing stays in the UI (requires clinical supervision). It is categorised as a Read tool in the Servicialo MCP Server, which means it retrieves data without modifying state.
treatment_plans_list accepts 7 parameters: page, limit, apiKey, status, orgSlug, clientId, proveedorId. 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 treatment_plans_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.
treatment_plans_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 treatment_plans_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 treatment_plans_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.
treatment_plans_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