get_plan_status

Show the current organisation plan, subscription/payment state, enabled modules, and quota usage. Use before deciding whether an agentic operation is allowed.

SERVERFavCRM SOURCEhttps://api.favcrm.io/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-favcrm-favcrm/get-plan-status.md

WHAT IT DOES

What get_plan_status does on FavCRM

AI agents call get_plan_status 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.

RISK

Why get_plan_status is rated Low

This tool retrieves and displays system status information about subscription state, enabled modules, and quota usage. It performs no modifications, deletions, or external operations. While it touches financial data (subscription/payment state), it only reads this information without moving money or committing financial obligations.

From the tool's definition Tool description states 'Show the current organisation plan, subscription/payment state, enabled modules, and quota usage' — purely informational retrieval with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_plan_status 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_plan_status, this is the rule to start with:

get_plan_status Allowed

get_plan_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_plan_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect FavCRM, apply this rule, and every get_plan_status call is checked against it from then on.

FAQ

Questions about get_plan_status

What does the get_plan_status tool do? +

Show the current organisation plan, subscription/payment state, enabled modules, and quota usage. Use before deciding whether an agentic operation is allowed. It is categorised as a Read tool in the FavCRM MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_plan_status? +

Register the FavCRM MCP server in PolicyLayer and add a rule for get_plan_status: 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_plan_status? +

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

Can I rate-limit get_plan_status? +

Yes. Add a rate_limit block to the get_plan_status 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_plan_status completely? +

Set action: deny in the PolicyLayer policy for get_plan_status. 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_plan_status? +

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

KEEP EXPLORING

More on FavCRM, and thousands of servers like it.

This server

All 220 FavCRM tools →

Across the catalogue

get_task_status on 0rca Dojo MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →