get_service_detail

Get full service details including addons, staff, resources, and tier pricing.

SERVERFavCRM SOURCEhttps://api.favcrm.io/mcp
Low RISK CLASS
Category Read
Parameters 11 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

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

Questions about get_service_detail

What does the get_service_detail tool do? +

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.

What parameters does get_service_detail accept? +

get_service_detail accepts 1 parameter: serviceId. Required: serviceId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_service_detail? +

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.

What risk level is get_service_detail? +

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

Can I rate-limit get_service_detail? +

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.

How do I block get_service_detail completely? +

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.

What MCP server provides get_service_detail? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of FavCRM's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.