get_subscription_status

THE RISK

Low Risk

Why get_subscription_status needs a policy

This tool retrieves subscription metadata without modifying data or executing transactions. It is a read-only query operation. While it touches billing data, it does not move money or commit financial obligations, so it does not qualify as Financial.

From the tool's definition Tool name 'get_subscription_status' and description indicate retrieval of subscription status information. No modification, deletion, or financial transactions are performed—only querying existing billing/subscription state.

Documented attack patterns abuse exactly the kind of access get_subscription_status gives an agent:

POLICY

How to control get_subscription_status

PolicyLayer is an MCP gateway — it sits between your AI agents and Todo MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_subscription_status:

policy.json

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

get_subscription_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Todo MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Todo MCP Server tools

Financial upgrade_subscription Upgrade user subscription to paid plan Destructive delete_todo Delete a todo item with interactive prompts Destructive logout Logout and clear stored authentication token Write create_todo Create a new todo item with interactive prompts Write save_token Save your Kinde authentication token for future use Write update_todo Update an existing todo item with interactive prompts Read get_kinde_billing Get Kinde billing information and subscription status Read list_todos List all todos for the authenticated user

All 11 Todo MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_subscription_status

What does the get_subscription_status tool do? +

Get the user\. It is categorised as a Read tool in the Todo MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_subscription_status? +

Register the Todo MCP Server 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 Todo MCP Server. 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 Todo MCP Server MCP server (sholajegede/todo_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Todo MCP Server tool call.

Start from Todo MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →