planka_delete_custom_field_group

Delete a custom field group

Server Planka MCP Server for Claude nextheberg/planka-mcp-server-for-claude
Category Destructive
Risk class Critical
Parameters 00 required

What planka_delete_custom_field_group does on Planka MCP Server for Claude

AI agents call planka_delete_custom_field_group to permanently remove resources in Planka MCP Server for Claude — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why planka_delete_custom_field_group needs a policy

The tool performs an irreversible deletion operation on a custom field group within a Planka project management system. While the blast radius is scoped to removing field group metadata (not user data or financial systems), the deletion cannot be undone and may disrupt workflows that depend on those field definitions. This fits the Destructive category as it permanently removes data structures.

From the tool's definition Tool name contains 'delete' and description explicitly states 'Delete a custom field group'; this irreversibly removes a custom field group configuration.

Questions about planka_delete_custom_field_group

What does the planka_delete_custom_field_group tool do? +

Delete a custom field group. It is categorised as a Destructive tool in the Planka MCP Server for Claude 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 planka_delete_custom_field_group? +

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

What risk level is planka_delete_custom_field_group? +

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

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

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

planka_delete_custom_field_group is provided by the Planka MCP Server for Claude MCP server (nextheberg/planka-mcp-server-for-claude). 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.