AI agents use create_relations to create or update resources in MCP Memory LibSQL — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Memory LibSQL environment.
The tool creates or establishes new relationships between entities in the knowledge graph, which is a reversible modification of data. It does not delete data (hence not Destructive), does not execute arbitrary code (hence not Execute), and does not involve financial transactions.
From the tool's definition Tool name is 'create_relations' and description states 'Create relations between entities'. This creates/establishes new relationships in a persistent memory system backed by libSQL.
Documented attack patterns abuse exactly the kind of access create_relations gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Memory LibSQL, and nothing reaches the server without passing your rules. This is the rule we recommend for create_relations:
{
"version": "1",
"default": "deny",
"tools": {
"create_relations": {
"limits": [
{
"counter": "create_relations_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_relations 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.
Create relations between entities. It is categorised as a Write tool in the MCP Memory LibSQL MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Memory LibSQL MCP server in PolicyLayer and add a rule for create_relations: 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 MCP Memory LibSQL. Nothing to install.
create_relations 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 create_relations 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 create_relations. 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.
create_relations is provided by the MCP Memory LibSQL MCP server (joleyline/mcp-memory-libsql). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Memory LibSQL, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 MCP Memory LibSQL tools catalogued and risk-classified — across an index of 43,000+ MCP servers.