append_project_fact
v2.1.0 \u2014 Append one fact to a project context (auto-creates the record on first call; dedups).
This record as markdown: /tools/danielsimonjr-memory-mcp/append-project-fact.md
What append_project_fact does on Enhanced Knowledge Graph Memory Server
AI agents use append_project_fact to create or update resources in Enhanced Knowledge Graph Memory Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Enhanced Knowledge Graph Memory Server environment.
Why append_project_fact is rated Medium
This tool writes data by appending a fact to a project context record. It creates or modifies data reversibly — facts can be removed or overwritten. Auto-creation on first call and deduplication are write operations with no destructive, financial, or execution implications. Severity is low since it only adds structured knowledge graph entries.
From the tool's definition 'Append one fact to a project context (auto-creates the record on first call; dedups)'
Attacks that exploit this kind of access
The rule that runs append_project_fact safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Enhanced Knowledge Graph Memory Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For append_project_fact, this is the rule to start with:
append_project_fact 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Enhanced Knowledge Graph Memory Server, apply this rule, and every append_project_fact call is checked against it from then on.
Questions about append_project_fact
v2.1.0 \u2014 Append one fact to a project context (auto-creates the record on first call; dedups). It is categorised as a Write tool in the Enhanced Knowledge Graph Memory Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Enhanced Knowledge Graph Memory Server MCP server in PolicyLayer and add a rule for append_project_fact: 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 Enhanced Knowledge Graph Memory Server. Nothing to install.
append_project_fact 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 append_project_fact 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 append_project_fact. 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.
append_project_fact is provided by the Enhanced Knowledge Graph Memory Server MCP server (danielsimonjr/memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Enhanced Knowledge Graph Memory Server, and thousands of servers like it.
Across the catalogue