get_subscription_status

Get the current subscription status, plan tier, and feature limits for the authenticated ${persona}.

SERVERBusinys SOURCE@businys/mcp-server

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/app-businys-mcp-server/get-subscription-status.md

WHAT IT DOES

What get_subscription_status does on Businys

AI agents call get_subscription_status to retrieve information from Businys 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_subscription_status is rated Low

This tool retrieves information about an authenticated user's subscription details without creating, modifying, deleting, or executing any operations. It is a straightforward data query that returns configuration and status information.

From the tool's definition Tool description states 'Get the current subscription status, plan tier, and feature limits' — a retrieval operation with no modification or side effects. The verb 'get' and the query nature (status check) are characteristic of Read operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_subscription_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Businys, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_subscription_status, this is the rule to start with:

get_subscription_status Allowed

get_subscription_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_subscription_status": {}
  }
}

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

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

FAQ

Questions about get_subscription_status

What does the get_subscription_status tool do? +

Get the current subscription status, plan tier, and feature limits for the authenticated ${persona}. It is categorised as a Read tool in the Businys MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_subscription_status? +

Register the Businys MCP server in PolicyLayer and add a rule for get_subscription_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 Businys. Nothing to install.

What risk level is get_subscription_status? +

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

Can I rate-limit get_subscription_status? +

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

Set action: deny in the PolicyLayer policy for get_subscription_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_subscription_status? +

get_subscription_status is provided by the Businys MCP server (@businys/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Businys, and thousands of servers like it.

This server

All 248 Businys tools →

Across the catalogue

aiva_get_subscription on AIVA MCP Server →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 → The MCP Attack Database →

Guides

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