Transfer a subscription from one user to another.
AI agents use transfer_subscription to commit financial operations through OneSignal MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
transfer_subscription moves real money, and an autonomous agent will call it with the same confidence it calls a search tool. A misread instruction or an injected prompt is all it takes to drain an account or blow a budget.
Attacks that exploit this kind of access
Transfer a subscription from one user to another. It is categorised as a Financial tool in the OneSignal MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the OneSignal MCP Server MCP server in PolicyLayer and add a rule for transfer_subscription: 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 OneSignal MCP Server. Nothing to install.
transfer_subscription 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 transfer_subscription 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 transfer_subscription. 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.
transfer_subscription is provided by the OneSignal MCP Server MCP server (weirdbrains/onesignal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.