agent_subscribe_white_label
Start a White Label subscription with a Stripe PaymentMethod. Its own subscription; no mail
This record as markdown: /tools/trekmail-mcp-server/agent-subscribe-white-label.md
What agent_subscribe_white_label does on TrekMail MCP Server
AI agents use agent_subscribe_white_label to commit financial operations through TrekMail MCP Server, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why agent_subscribe_white_label is rated Critical
Initiates a paid subscription using Stripe, directly committing a financial obligation.
From the tool's definition Start a White Label subscription with a Stripe PaymentMethod
Attacks that exploit this kind of access
The rule that runs agent_subscribe_white_label safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TrekMail MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For agent_subscribe_white_label, this is the rule to start with:
Any call to agent_subscribe_white_label is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect TrekMail MCP Server, apply this rule, and every agent_subscribe_white_label call is checked against it from then on.
Questions about agent_subscribe_white_label
Start a White Label subscription with a Stripe PaymentMethod. Its own subscription; no mail. It is categorised as a Financial tool in the TrekMail MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for agent_subscribe_white_label: 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 TrekMail MCP Server. Nothing to install.
agent_subscribe_white_label is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the agent_subscribe_white_label 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 agent_subscribe_white_label. 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.
agent_subscribe_white_label is provided by the TrekMail MCP Server MCP server (trekmail/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on TrekMail MCP Server, and thousands of servers like it.
Across the catalogue