MCP Server Policy
MEMORY MCP POLICY
Enforce policies on every tool call to the Memory MCP Server. 9 tools listed, categorised, and ready for rules.
GET STARTED
Download this policy scaffold and add your rules. Intercept enforces them on every tool call before it reaches Memory.
# Download policy scaffold
curl -o memory.yaml https://raw.githubusercontent.com/policylayer/intercept/main/policies/memory.yaml
# Run with Intercept
intercept --policy memory.yaml -- npx -y @modelcontextprotocol/server-memory Server documentation: https://github.com/modelcontextprotocol/servers/tree/main/src/memory
READ TOOLS
2WRITE TOOLS
3DESTRUCTIVE TOOLS
3OTHER TOOLS
1POLICY YAML
This scaffold lists every tool with empty rules. Add conditions — rate limits, argument validation, deny rules — then deploy with Intercept.
version: "1"
description: "Policy for modelcontextprotocol/server-memory"
default: "allow"
tools:
read_graph:
rules: []
search_nodes:
rules: []
add_observations:
rules: []
create_entities:
rules: []
create_relations:
rules: []
delete_entities:
rules: []
delete_observations:
rules: []
delete_relations:
rules: []
open_nodes:
rules: []RELATED POLICIES
FREQUENTLY ASKED QUESTIONS
What tools does the Memory MCP server expose?
The Memory MCP Server exposes 9 tools across 4 categories: Read, Write, Destructive, Other. Each tool can be individually controlled with Intercept policies.
How do I enforce policies on Memory?
Download the policy scaffold, add rules (rate limits, argument validation, deny rules), then run Intercept as a proxy in front of the Memory MCP server. Every tool call is evaluated against your YAML policy before execution.
Is the Memory policy free to use?
Yes. All Intercept policies are open source under the Apache 2.0 licence. Download, modify, and deploy without restrictions.
ENFORCE POLICIES ON MEMORY
Open source. One binary. Zero dependencies.