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 sha...
Bulk/mass operation — affects multiple targets
Part of the Pūrmemo MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
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. Intercept'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.
tools:
share_memory:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Pūrmemo policy for all 11 tools.
Agents calling write-class tools like share_memory have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
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.
Add a rule in your Intercept YAML policy under the tools section for share_memory. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Pūrmemo MCP server.
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 Intercept 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 Intercept 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). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept