활성 프로젝트를 변경합니다. 변경 후 해당 프로젝트 데이터를 즉시 로드합니다
AI agents use switch_project to create or update resources in Remote Memory MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Remote Memory MCP Server environment.
switch_project modifies application state (the active project context) and triggers data loading, making it a Write operation rather than Read. It is not Destructive because switching projects is reversible (another project can be selected). It is not Execute because it doesn't run arbitrary code or shell commands.
From the tool's definition Tool description (translated from Korean) states: 'Change the active project. After changing, immediately load the project data.' This involves switching context and loading project data, which constitutes a state modification operation.
Attacks that exploit this kind of access
활성 프로젝트를 변경합니다. 변경 후 해당 프로젝트 데이터를 즉시 로드합니다. It is categorised as a Write tool in the Remote Memory MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Remote Memory MCP Server MCP server in PolicyLayer and add a rule for switch_project: 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 Remote Memory MCP Server. Nothing to install.
switch_project 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 switch_project 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 switch_project. 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.
switch_project is provided by the Remote Memory MCP Server MCP server (yeomyujun/remote-memory-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →