project_link_feature
Link an existing owned parentless epic to this project. Exact retry reuses the link; linking an epic already belonging to another project conflicts. Does not reparent, claim or execute the ticket.
This record as markdown: /tools/com-meta-council-decision-intelligence/project-link-feature.md
What project_link_feature does on Meta Council
AI agents invoke project_link_feature to trigger actions in Meta Council. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
ticket_id | string | Yes | |
project_id | string | Yes |
Parameters from the server's own tool schema.
Why project_link_feature is rated High
project_link_feature triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs project_link_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_link_feature, this is the rule to start with:
project_link_feature stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Meta Council, apply this rule, and every project_link_feature call is checked against it from then on.
Questions about project_link_feature
Link an existing owned parentless epic to this project. Exact retry reuses the link; linking an epic already belonging to another project conflicts. Does not reparent, claim or execute the ticket. It is categorised as a Execute tool in the Meta Council MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
project_link_feature accepts 2 parameters: ticket_id, project_id. Required: ticket_id, project_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_link_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_link_feature is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the project_link_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_link_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_link_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