check_plan_operation
Preflight whether an intended operation is allowed by token scopes, enabled modules, subscription state, and quota. Provide toolName, quotaCode, or moduleCode.
This record as markdown: /tools/io-favcrm-favcrm/check-plan-operation.md
What check_plan_operation does on FavCRM
AI agents call check_plan_operation 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 |
|---|---|---|---|
delta | integer | — | Planned usage increment. Currently quota checks are single-resource preflights. |
toolName | string | — | MCP tool name to preflight, e.g. create_account |
quotaCode | string | — | Quota code to check, e.g. contacts or mcp_calls_per_minute |
moduleCode | string | — | Module code to check, e.g. whatsapp or crm |
Parameters from the server's own tool schema.
Why check_plan_operation is rated Low
This tool retrieves authorization and quota information to inform whether operations are permitted. It performs no mutations, deletions, financial transactions, or external executions. The input parameters (toolName, quotaCode, moduleCode) are lookup keys, not operation triggers. This is a read-only permissions check, consistent with other Read category tools that query system state.
From the tool's definition Tool description states it 'Preflight[s] whether an intended operation is allowed' — a pure validation/query operation that checks permissions, modules, and quotas without modifying any data or triggering side effects.
Attacks that exploit this kind of access
The rule that runs check_plan_operation 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 check_plan_operation, this is the rule to start with:
check_plan_operation 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 check_plan_operation call is checked against it from then on.
Questions about check_plan_operation
Preflight whether an intended operation is allowed by token scopes, enabled modules, subscription state, and quota. Provide toolName, quotaCode, or moduleCode. It is categorised as a Read tool in the FavCRM MCP Server, which means it retrieves data without modifying state.
check_plan_operation accepts 4 parameters: delta, toolName, quotaCode, moduleCode. 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 check_plan_operation: 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.
check_plan_operation 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 check_plan_operation 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 check_plan_operation. 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.
check_plan_operation 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