delete_plan
A destructive tool on the PineLabs Plural PG — Payment Gateway MCP server.
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.
Attacks that exploit this kind of access
The rule that runs delete_plan safely
PolicyLayer is an MCP gateway: it sits between your AI agents and PineLabs Plural PG — Payment Gateway MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_plan, this is the rule to start with:
delete_plan is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect PineLabs Plural PG — Payment Gateway MCP Server, apply this rule, and every delete_plan call is checked against it from then on.
Questions about delete_plan
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.
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.
delete_plan is a Destructive 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 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.
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.
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.
This server
Across the catalogue