Add a temporal fact (subject, predicate, object) to the graph.
AI agents use mnemostack_graph_add_triple to create or update resources in Mnemostack — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mnemostack environment.
An AI agent can call mnemostack_graph_add_triple faster than any human can review — one bad instruction and it creates or modifies resources in Mnemostack by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Add a temporal fact (subject, predicate, object) to the graph. It is categorised as a Write tool in the Mnemostack MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mnemostack MCP server in PolicyLayer and add a rule for mnemostack_graph_add_triple: 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 Mnemostack. Nothing to install.
mnemostack_graph_add_triple 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 mnemostack_graph_add_triple 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 mnemostack_graph_add_triple. 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.
mnemostack_graph_add_triple is provided by the Mnemostack MCP server (udjin-labs/mnemostack). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.