project_unlink_feature
Remove one exact project-feature placement, retaining the ticket. Read binding_id from project_get first; stale bindings or document references conflict. Does not delete tickets or documents.
This record as markdown: /tools/com-meta-council-decision-intelligence/project-unlink-feature.md
What project_unlink_feature does on Meta Council
AI agents call project_unlink_feature to permanently remove resources in Meta Council, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
ticket_id | string | Yes | |
project_id | string | Yes | |
expected_binding_id | string | Yes |
Parameters from the server's own tool schema.
Why project_unlink_feature is rated Critical
An AI agent that decides to call project_unlink_feature doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Meta Council is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs project_unlink_feature safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Council, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For project_unlink_feature, this is the rule to start with:
project_unlink_feature 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 Meta Council, apply this rule, and every project_unlink_feature call is checked against it from then on.
Questions about project_unlink_feature
Remove one exact project-feature placement, retaining the ticket. Read binding_id from project_get first; stale bindings or document references conflict. Does not delete tickets or documents. It is categorised as a Destructive tool in the Meta Council MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
project_unlink_feature accepts 3 parameters: ticket_id, project_id, expected_binding_id. Required: ticket_id, project_id, expected_binding_id. The full parameter table on this page comes from the server's own tool schema.
Register the Meta Council MCP server in PolicyLayer and add a rule for project_unlink_feature: 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 Meta Council. Nothing to install.
project_unlink_feature 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 project_unlink_feature 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 project_unlink_feature. 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.
project_unlink_feature is provided by the Meta Council MCP server (https://meta-council.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meta Council, and thousands of servers like it.
Across the catalogue