Set the visibility of a memory you own. VISIBILITY LEVELS: - private: Only you can see it (default) - unlisted: Anyone with the direct link can view it - public: Discoverable in the community tab by all users WHEN TO USE: - User says "share this memory" or "make this public" - User wants to share...
Risk signalsBulk/mass operation — affects multiple targets
Part of the Pūrmemo server.
Free to start. No card required.
AI agents use share_memory to create or modify resources in Pūrmemo. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call share_memory repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Pūrmemo.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"share_memory": {
"limits": [
{
"counter": "share_memory_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Pūrmemo policy for all 11 tools.
These attack patterns abuse exactly the kind of access share_memory gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Set the visibility of a memory you own. VISIBILITY LEVELS: - private: Only you can see it (default) - unlisted: Anyone with the direct link can view it - public: Discoverable in the community tab by all users WHEN TO USE: - User says "share this memory" or "make this public" - User wants to share knowledge with the community - User wants to generate a shareable link QUOTA: - Free tier: 5 shares/month - Pro/Teams: Unlimited EXAMPLE: share_memory({ memory_id: "abc-123", visibility: "public" }) RETURNS: Updated visibility status and confirmation message.. It is categorised as a Write tool in the Pūrmemo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pūrmemo MCP server in PolicyLayer and add a rule for share_memory: 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 Pūrmemo. Nothing to install.
share_memory 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 share_memory 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 share_memory. 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.
share_memory is provided by the Pūrmemo MCP server (purmemo/purmemo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 11 Pūrmemo tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.