agendas_get

Get complete details of a public agenda by ID. Returns all configuration including booking flow (service_first, provider_first, auto), selection modes, assignment strategy, privacy settings, linked provider/service, and session count. Use before agendas_update to inspect current settings.

SERVERServicialo SOURCE@servicialo/mcp-server

Low RISK CLASS

Category Read

Parameters 32 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What agendas_get does on Servicialo

AI agents call agendas_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
`apiKey`	string	—
`orgSlug`	string	Yes
`agendaId`	string	Yes

Parameters from the server's own tool schema.

RISK

Why agendas_get is rated Low

Retrieves agenda configuration data without modifying or deleting anything.

From the tool's definition Get complete details of a public agenda by ID. Returns all configuration.

Risk signalsHandles credentials or secrets (apiKey)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

agendas_get Allowed

agendas_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": {
    "agendas_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 agendas_get call is checked against it from then on.

FAQ

Questions about agendas_get

What does the agendas_get tool do? +

What parameters does agendas_get accept? +

agendas_get accepts 3 parameters: apiKey, orgSlug, agendaId. Required: orgSlug, agendaId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on agendas_get? +

Register the Servicialo MCP server in PolicyLayer and add a rule for agendas_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 agendas_get? +

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

Can I rate-limit agendas_get? +

Yes. Add a rate_limit block to the agendas_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 agendas_get completely? +

Set action: deny in the PolicyLayer policy for agendas_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 agendas_get? +

agendas_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 →