delete_plan

A destructive tool on the PineLabs Plural PG — Payment Gateway MCP server.

Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-plural-pinelabs-pinelabs-online-mcp/delete-plan.md

What delete_plan does on PineLabs Plural PG — Payment Gateway MCP Server

AI agents call delete_plan to permanently remove resources in PineLabs Plural PG — Payment Gateway MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_plan is rated Critical

Deletion of a subscription plan on a payment gateway is a destructive action that cannot be undone and affects live subscription infrastructure. This ranks as Destructive rather than Financial because the primary operation is data destruction; however, the impact is critical due to the financial systems affected.

From the tool's definition Tool name is 'delete_plan' on a payment gateway server. Server context involves subscriptions and financial operations. 'Delete' indicates irreversible removal.

Questions about delete_plan

What does the delete_plan tool do? +

delete_plan is a destructive tool on the PineLabs Plural PG — Payment Gateway MCP Server MCP server. It is categorised as a Destructive tool in the PineLabs Plural PG — Payment Gateway MCP Server 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 delete_plan? +

Register the PineLabs Plural PG — Payment Gateway MCP Server MCP server in PolicyLayer and add a rule for delete_plan: 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 PineLabs Plural PG — Payment Gateway MCP Server. Nothing to install.

What risk level is delete_plan? +

delete_plan 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 delete_plan? +

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

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

delete_plan is provided by the PineLabs Plural PG — Payment Gateway MCP Server MCP server (pypi:pinelabs-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on PineLabs Plural PG — Payment Gateway MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of PineLabs Plural PG — Payment Gateway MCP Server's. Pull the full record:

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.