get_service_detail
Get full service details including addons, staff, resources, and tier pricing.
This record as markdown: /tools/io-favcrm-favcrm/get-service-detail.md
What get_service_detail does on FavCRM
AI agents call get_service_detail 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 |
|---|---|---|---|
serviceId | string | Yes | The service ID |
Parameters from the server's own tool schema.
Why get_service_detail is rated Low
This tool retrieves and queries service configuration data (addons, staff, resources, pricing tiers) without creating, modifying, deleting, or executing operations. It is a straightforward read operation with no destructive, financial, or execution capabilities. The blast radius of misuse is minimal — an attacker gains visibility into service details but cannot alter bookings, payments, or system state.
From the tool's definition Tool name 'get_service_detail' and description 'Get full service details' — uses 'Get' verb indicating data retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_service_detail 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_detail, this is the rule to start with:
get_service_detail 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_detail call is checked against it from then on.
Questions about get_service_detail
Get full service details including addons, staff, resources, and tier pricing. It is categorised as a Read tool in the FavCRM MCP Server, which means it retrieves data without modifying state.
get_service_detail accepts 1 parameter: serviceId. Required: serviceId. 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_detail: 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_detail 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_detail 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_detail. 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_detail 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