share_memory
Share a memory namespace with another handle. Permission is 'read' (read-only) or 'write' (read + write + delete). Owner only — registered handle + secret required.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/share-memory.md
What share_memory does on Gateway
AI agents use share_memory to create or update resources in Gateway, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gateway environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
handle | string | Yes | owner handle (you) |
secret | string | — | |
grantee | string | Yes | handle to share with |
namespace | string | Yes | namespace to share |
permission | string | Yes |
Parameters from the server's own tool schema.
Why share_memory is rated Medium
This tool modifies access control settings on a memory namespace by granting permissions to another handle. It creates or updates a sharing relationship, which is a reversible write operation. While the 'write' permission granted could enable destructive actions downstream (delete), the tool itself is only modifying access controls, not deleting data.
From the tool's definition Share a memory namespace with another handle. Permission is 'read' (read-only) or 'write' (read + write + delete). Owner only — registered handle + secret required.
Risk signalsHandles credentials or secrets (secret)
Attacks that exploit this kind of access
The rule that runs share_memory safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For share_memory, this is the rule to start with:
share_memory 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 Gateway, apply this rule, and every share_memory call is checked against it from then on.
Questions about share_memory
Share a memory namespace with another handle. Permission is 'read' (read-only) or 'write' (read + write + delete). Owner only — registered handle + secret required. It is categorised as a Write tool in the Gateway MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
share_memory accepts 5 parameters: handle, secret, grantee, namespace, permission. Required: handle, grantee, namespace, permission. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway 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 Gateway. 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 Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue