provider_get
Get complete details of a provider including services, schedule, and session stats.
This record as markdown: /tools/com-servicialo-mcp-server/provider-get.md
What provider_get does on Servicialo
AI agents call provider_get 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 |
|---|---|---|---|
apiKey | string | — | |
orgSlug | string | Yes | |
providerId | string | Yes |
Parameters from the server's own tool schema.
Why provider_get is rated Low
This tool retrieves and queries provider information without side effects. It does not create, modify, delete, or execute any operations. The blast radius of misuse is minimal—an agent could access provider details it shouldn't, but cannot alter or destroy data. Classified as Read with low severity.
From the tool's definition Tool name 'provider_get' and description 'Get complete details of a provider' indicates data retrieval with no modification or deletion. The action is purely informational, fetching provider details, services, schedule, and session stats.
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs provider_get 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 provider_get, this is the rule to start with:
provider_get 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 provider_get call is checked against it from then on.
Questions about provider_get
Get complete details of a provider including services, schedule, and session stats. It is categorised as a Read tool in the Servicialo MCP Server, which means it retrieves data without modifying state.
provider_get accepts 3 parameters: apiKey, orgSlug, providerId. Required: orgSlug, providerId. 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 provider_get: 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.
provider_get 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 provider_get 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 provider_get. 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.
provider_get 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