madeonsol_first_touch_subscriptions_delete

Delete a first-touch subscription permanently. ULTRA only.

Server Madeonsol mcp-server-madeonsol
Category Destructive
Risk class Critical
Parameters 00 required

What madeonsol_first_touch_subscriptions_delete does on Madeonsol

AI agents call madeonsol_first_touch_subscriptions_delete to permanently remove resources in Madeonsol — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why madeonsol_first_touch_subscriptions_delete needs a policy

This tool irreversibly deletes subscription data without the ability to undo the action. Even though the blast radius is somewhat limited to subscription records (not financial transactions themselves), permanent deletion of data is classified as Destructive per the taxonomy. The high severity reflects that an AI agent misusing this could permanently remove important subscription configurations or records for users.

From the tool's definition Tool name contains 'delete' and description explicitly states 'Delete a first-touch subscription permanently.' The word 'permanently' indicates an irreversible operation.

Questions about madeonsol_first_touch_subscriptions_delete

What does the madeonsol_first_touch_subscriptions_delete tool do? +

Delete a first-touch subscription permanently. ULTRA only. It is categorised as a Destructive tool in the Madeonsol MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on madeonsol_first_touch_subscriptions_delete? +

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

What risk level is madeonsol_first_touch_subscriptions_delete? +

madeonsol_first_touch_subscriptions_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit madeonsol_first_touch_subscriptions_delete? +

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

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

madeonsol_first_touch_subscriptions_delete is provided by the Madeonsol MCP server (mcp-server-madeonsol). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.