AI agents use update_entity 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.
The tool modifies entity data reversibly within the persistent knowledge base. It is categorized as Write rather than Destructive because updates are generally reversible (the prior state can be restored). Severity is medium: an agent misusing this could corrupt or alter stored knowledge, but the effect is confined to the storage layer and reversible.
From the tool's definition Tool named 'update_entity' on a knowledge/storage MCP server. Sibling tools include 'create_entity' (Write), 'delete_entity' (Destructive), and other data-management operations. The 'update_' prefix indicates modification of existing data.
Documented attack patterns abuse exactly the kind of access update_entity 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 update_entity:
{
"version": "1",
"default": "deny",
"tools": {
"update_entity": {
"limits": [
{
"counter": "update_entity_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_entity 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.
update_entity. 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 update_entity: 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.
update_entity 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 update_entity 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 update_entity. 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.
update_entity 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.