Unlink entity from project (removes organizational grouping). WHEN: When an entity-project association is no longer relevant or was created in error. BEHAVIOR: Removes association between entity and project. Safe to call even if link doesn't exist (returns False). Entity and project remain intact...
AI agents use unlink_entity_from_project to create or update resources in Forgetful — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Forgetful environment.
This tool modifies metadata by removing a relationship/association between two entities, which is a Write operation. It is not Destructive because the entity and project themselves are preserved and the action is reversible (the link can be re-established).
From the tool's definition The tool description explicitly states it 'Removes association between entity and project' and that 'Entity and project remain intact.' This is a reversible modification operation that alters the organizational structure without deleting or destroying data.
Documented attack patterns abuse exactly the kind of access unlink_entity_from_project gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Forgetful, and nothing reaches the server without passing your rules. This is the rule we recommend for unlink_entity_from_project:
{
"version": "1",
"default": "deny",
"tools": {
"unlink_entity_from_project": {
"limits": [
{
"counter": "unlink_entity_from_project_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}unlink_entity_from_project stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Unlink entity from project (removes organizational grouping). WHEN: When an entity-project association is no longer relevant or was created in error. BEHAVIOR: Removes association between entity and project. Safe to call even if link doesn't exist (returns False). Entity and project remain intact. Args: entity_id: Entity ID to unlink project_id: Project ID to unlink ctx: Context (automatically injected) Returns: True if link was removed, False if link didn't exist Raises: ToolError: If unlinking fails. It is categorised as a Write tool in the Forgetful MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Forgetful MCP server in PolicyLayer and add a rule for unlink_entity_from_project: 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 Forgetful. Nothing to install.
unlink_entity_from_project is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the unlink_entity_from_project 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 unlink_entity_from_project. 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.
unlink_entity_from_project is provided by the Forgetful MCP server (scottrbk/forgetful). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 59 Forgetful tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
59 Forgetful tools catalogued and risk-classified — across an index of 42,500+ MCP servers.