새 프로젝트를 생성합니다
AI agents use create_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.
This tool creates new data structures (projects) within the knowledge graph system. Creation is a reversible write operation—projects can be modified or deleted. It does not execute arbitrary code, trigger external operations with unpredictable effects, delete data irreversibly, or involve financial transactions.
From the tool's definition Tool name 'create_project' and description indicating creation of new projects ('새 프로젝트를 생성합니다' = 'Creates a new project'). Aligned with sibling tools like 'create_entities', 'create_relations', and 'create_backup' which are reversible write operations.
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 create_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.
create_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 create_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 create_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.
create_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 →