Link entity to project (organizational grouping). WHEN: When an entity belongs to or is relevant to a specific project. Creates association so the entity can be filtered by project. BEHAVIOR: Creates association between entity and project. Idempotent - safe to call multiple times (won't create du...
AI agents use link_entity_to_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 the knowledge base by creating a relationship between two existing entities, but the operation is reversible (links can presumably be removed) and has no destructive or external side effects. The blast radius of misuse is minimal—incorrect associations would cause organizational confusion but no data loss or irreversible harm. The idempotent nature further reduces risk.
From the tool's definition Tool creates an association/link between an entity and a project. Description states: 'Creates association between entity and project' and 'Creates association so the entity can be filtered by project.' This is a reversible modification that organizes…
Documented attack patterns abuse exactly the kind of access link_entity_to_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 link_entity_to_project:
{
"version": "1",
"default": "deny",
"tools": {
"link_entity_to_project": {
"limits": [
{
"counter": "link_entity_to_project_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}link_entity_to_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.
Link entity to project (organizational grouping). WHEN: When an entity belongs to or is relevant to a specific project. Creates association so the entity can be filtered by project. BEHAVIOR: Creates association between entity and project. Idempotent - safe to call multiple times (won't create duplicates). Both entity and project must exist and be owned by the user. Examples: # Associate a team member with a project: link_entity_to_project(entity_id=5, project_id=1) # Associate a system/server with an infrastructure project: link_entity_to_project(entity_id=12, project_id=3) Args: entity_id: Entity ID to link project_id: Project ID to link ctx: Context (automatically injected) Returns: True if linked successfully (or already linked) Raises: ToolError: If entity or project not found or not owned by user. 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 link_entity_to_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.
link_entity_to_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 link_entity_to_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 link_entity_to_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.
link_entity_to_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.