AI agents use create_preset to create or update resources in myAI Memory Sync — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your myAI Memory Sync environment.
This tool creates new presets that persist across Claude interfaces. While reversible (presets can be deleted or overwritten), it modifies the user's stored configuration state. The risk is medium because misuse could pollute the user's preference system with unwanted presets, requiring manual cleanup, but causes no irreversible data loss and no financial impact.
From the tool's definition Tool name 'create_preset' indicates creation of new preset data. Sibling tools like 'load_preset', 'update_section', and 'update_template' confirm this server manages persistent user preferences and configurations.
Documented attack patterns abuse exactly the kind of access create_preset gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and myAI Memory Sync, and nothing reaches the server without passing your rules. This is the rule we recommend for create_preset:
{
"version": "1",
"default": "deny",
"tools": {
"create_preset": {
"limits": [
{
"counter": "create_preset_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_preset 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_preset. It is categorised as a Write tool in the myAI Memory Sync MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the myAI Memory Sync MCP server in PolicyLayer and add a rule for create_preset: 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 myAI Memory Sync. Nothing to install.
create_preset 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_preset 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_preset. 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_preset is provided by the myAI Memory Sync MCP server (jktfe/myaimemory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from myAI Memory Sync, 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.
10 myAI Memory Sync tools catalogued and risk-classified — across an index of 43,000+ MCP servers.