set_memory_visibility
Set the visibility of a memory entity for multi-agent access control. Auto-promotes plain entities to AgentEntity (stamps agentId/memoryType/etc.) instead of failing silently. Supports \u03B7.5.5.b extensions: allowedRoles (role gate), visibleFrom/visibleUntil (time-window gate).
This record as markdown: /tools/danielsimonjr-memory-mcp/set-memory-visibility.md
What set_memory_visibility does on Enhanced Knowledge Graph Memory Server
AI agents use set_memory_visibility to create or update resources in Enhanced Knowledge Graph Memory Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Enhanced Knowledge Graph Memory Server environment.
Why set_memory_visibility is rated Medium
An AI agent can call set_memory_visibility faster than any human can review: one bad instruction and it creates or modifies resources in Enhanced Knowledge Graph Memory Server by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs set_memory_visibility safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Enhanced Knowledge Graph Memory Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_memory_visibility, this is the rule to start with:
set_memory_visibility 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Enhanced Knowledge Graph Memory Server, apply this rule, and every set_memory_visibility call is checked against it from then on.
Questions about set_memory_visibility
Set the visibility of a memory entity for multi-agent access control. Auto-promotes plain entities to AgentEntity (stamps agentId/memoryType/etc.) instead of failing silently. Supports \u03B7.5.5.b extensions: allowedRoles (role gate), visibleFrom/visibleUntil (time-window gate). It is categorised as a Write tool in the Enhanced Knowledge Graph Memory Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Enhanced Knowledge Graph Memory Server MCP server in PolicyLayer and add a rule for set_memory_visibility: 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 Enhanced Knowledge Graph Memory Server. Nothing to install.
set_memory_visibility 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 set_memory_visibility 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 set_memory_visibility. 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.
set_memory_visibility is provided by the Enhanced Knowledge Graph Memory Server MCP server (danielsimonjr/memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Enhanced Knowledge Graph Memory Server, and thousands of servers like it.
Across the catalogue