set_project_scope
Set the active project scope for this server session. New entities passed without an explicit projectId may be auto-stamped with this value by scope-aware handlers; pass an empty string to clear the scope. Returns { projectId } where projectId is the new active scope (null when cleared).
This record as markdown: /tools/danielsimonjr-memory-mcp/set-project-scope.md
What set_project_scope does on Enhanced Knowledge Graph Memory Server
AI agents use set_project_scope 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_project_scope is rated Medium
This tool performs a state modification (Write category) by changing session configuration that affects how future entities are tagged. It is not Read (it modifies state, not just retrieves it), not Execute (it doesn't run code or external operations), not Destructive (changes are reversible by setting a different scope or clearing it), and not Financial (no monetary impact).
From the tool's definition The tool sets the active project scope, which modifies the session state configuration. The description indicates it updates internal session state (the 'active project scope') that governs how subsequent operations are stamped with metadata.
Attacks that exploit this kind of access
The rule that runs set_project_scope 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_project_scope, this is the rule to start with:
set_project_scope 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_project_scope call is checked against it from then on.
Questions about set_project_scope
Set the active project scope for this server session. New entities passed without an explicit projectId may be auto-stamped with this value by scope-aware handlers; pass an empty string to clear the scope. Returns { projectId } where projectId is the new active scope (null when cleared). 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_project_scope: 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_project_scope 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_project_scope 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_project_scope. 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_project_scope 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