Ingest a batch of already-normalized records directly into the store — the universal
AI agents use push to create or update resources in Lore — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lore environment.
This tool creates or modifies data records in a memory store reversibly. It does not delete data (ruling out Destructive), does not execute arbitrary code (ruling out Execute), and does not involve financial transactions.
From the tool's definition Tool name 'push' and description 'Ingest a batch of already-normalized records directly into the store' indicate data creation/modification without deletion.
Documented attack patterns abuse exactly the kind of access push gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Lore, and nothing reaches the server without passing your rules. This is the rule we recommend for push:
{
"version": "1",
"default": "deny",
"tools": {
"push": {
"limits": [
{
"counter": "push_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}push 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.
Ingest a batch of already-normalized records directly into the store — the universal. It is categorised as a Write tool in the Lore MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Lore MCP server in PolicyLayer and add a rule for push: 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 Lore. Nothing to install.
push 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 push 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 push. 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.
push is provided by the Lore MCP server (jordanhindo/lore). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Lore, 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.
8 Lore tools catalogued and risk-classified — across an index of 43,000+ MCP servers.