This record as markdown: /tools/io-favcrm-favcrm/get-order.md
What get_order does on FavCRM
AI agents call get_order 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 |
|---|---|---|---|
orderId | string | Yes | The order UUID |
Parameters from the server's own tool schema.
Why get_order is rated Low
This tool retrieves existing order data and returns it to the caller. It performs a read-only query with no side effects, fitting the Read category. The blast radius of misuse is low—an agent could access order data it shouldn't, but cannot modify, delete, or trigger financial transactions. Given the CRM context (bookings, customers, invoicing), this is a standard data retrieval endpoint.
From the tool's definition Tool name 'get_order' and description 'Get full order detail including line items' explicitly indicates a retrieval operation with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
The rule that runs get_order 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_order, this is the rule to start with:
get_order 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_order call is checked against it from then on.
Questions about get_order
Get full order detail including line items. It is categorised as a Read tool in the FavCRM MCP Server, which means it retrieves data without modifying state.
get_order accepts 1 parameter: orderId. Required: orderId. 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_order: 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_order 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_order 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_order. 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_order 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