settings_get

SERVERServicialo SOURCE@servicialo/mcp-server

Low RISK CLASS

Category Read

Parameters 51 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-servicialo-mcp-server/settings-get.md

WHAT IT DOES

What settings_get does on Servicialo

AI agents call settings_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
`keys`	string	—
`group`	string	—
`apiKey`	string	—
`chapter`	string	—
`orgSlug`	string	Yes

Parameters from the server's own tool schema.

RISK

Why settings_get is rated Low

Retrieves configuration data without modification. Medium severity due to sensitivity of organizational settings exposure.

From the tool's definition Get organization settings. Call it with no filters first to get the full map.

Risk signalsHandles credentials or secrets (apiKey)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs settings_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 settings_get, this is the rule to start with:

settings_get Allowed

settings_get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "settings_get": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Servicialo, apply this rule, and every settings_get call is checked against it from then on.

FAQ

Questions about settings_get

What does the settings_get tool do? +

Get organization settings. THIS IS THE ENTRY POINT for anything configurable: call it with no filters first to get the full map. Settings are indexed on two axes — group (the sections a human sees in the settings screen: profile, availability, client_fields, communication, reminders, automations, finances, delivery, cancellation, tax) and chapter (the onboarding-interview sequence: basics, availability, communication, finances, policies, reminders, client_data). Prefer group. Or pass keys for specific settings (comma-separated, e.g. "policies.noShowMaxStrikes,finances.clientPaymentTiming"). Covers ~88 keys including cancellation-policy tiers, granular reminder timing, dunning sequence, retention, delivery verification and the SII tax profile. The response also carries meta (label, type, valid options and dependencies per key) and panels — the configuration surfaces that are NOT scalar settings (bank accounts, payment credentials, API keys, members): each panel names the tools that cover it, or states why none does. It is categorised as a Read tool in the Servicialo MCP Server, which means it retrieves data without modifying state.

What parameters does settings_get accept? +

settings_get accepts 5 parameters: keys, group, apiKey, chapter, orgSlug. Required: orgSlug. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on settings_get? +

Register the Servicialo MCP server in PolicyLayer and add a rule for settings_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.

What risk level is settings_get? +

settings_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit settings_get? +

Yes. Add a rate_limit block to the settings_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.

How do I block settings_get completely? +

Set action: deny in the PolicyLayer policy for settings_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.

What MCP server provides settings_get? +

settings_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.

KEEP EXPLORING

More on Servicialo, and thousands of servers like it.

This server

All 111 Servicialo tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →