get_service_package
Get service package detail including applicability and selected booking service/event items.
This record as markdown: /tools/io-favcrm-favcrm/get-service-package.md
What get_service_package does on FavCRM
AI agents call get_service_package to retrieve information from FavCRM 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 |
|---|---|---|---|
packageId | string | Yes | Service package ID |
Parameters from the server's own tool schema.
Why get_service_package is rated Low
This tool retrieves information about service packages in the CRM system. It queries existing data structures (package details, applicability rules, associated booking items) but does not create, modify, delete, or execute any side effects. The blast radius of misuse is minimal—an agent could retrieve package information it shouldn't see, but cannot alter services, bookings, or customer data.
From the tool's definition Tool name 'get_service_package' with description 'Get service package detail including applicability and selected booking service/event items' indicates a retrieval operation.
Attacks that exploit this kind of access
The rule that runs get_service_package safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FavCRM, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_service_package, this is the rule to start with:
get_service_package 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 FavCRM, apply this rule, and every get_service_package call is checked against it from then on.
Questions about get_service_package
Get service package detail including applicability and selected booking service/event items. It is categorised as a Read tool in the FavCRM MCP Server, which means it retrieves data without modifying state.
get_service_package accepts 1 parameter: packageId. Required: packageId. The full parameter table on this page comes from the server's own tool schema.
Register the FavCRM MCP server in PolicyLayer and add a rule for get_service_package: 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 FavCRM. Nothing to install.
get_service_package 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 get_service_package 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 get_service_package. 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.
get_service_package is provided by the FavCRM MCP server (https://api.favcrm.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FavCRM, and thousands of servers like it.
This server
Across the catalogue