path-management

A set of rules for safely handling file paths in an MCP server, the service that connects an agent to external tools. It covers path cleanup, validation, access limits, and tracking directory changes.

In plain words
What is it for?
Use it when setting allowed project folders, resolving or joining paths, checking whether paths can be read or written, changing directories, and reporting path errors.
Why use it?
It reduces the risk of reading or writing files outside approved locations and makes different path formats behave consistently.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/r-huijts/xcode-mcp-server/path-management
Clone the repo
git clone --depth 1 https://github.com/r-huijts/xcode-mcp-server

Made for: Cursor.

Per session 1,477 This file is loaded in full into every session.
When invoked 1,477 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.01477 $0.01477
Opus 5 $0.00739 $0.00739
Sonnet 5 $0.00295 $0.00295
Haiku 4.5 $0.00148 $0.00148

Measured 2d ago against content hash 6580615b10ad, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

path-management scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/path-management.mdc · 205 lines

How it starts

The opening of the file, as written. The whole thing — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Path Management System

This document provides a detailed explanation of the path management system used in the MCP Server. It covers the architecture, components, workflows, and security considerations.

Overview

The path management system provides a centralized, secure, and consistent way to handle file paths and directory navigation throughout the application. It was designed to address several key challenges:

  1. Security: Prevent access to unauthorized parts of the filesystem
  2. Consistency: Handle diverse path formats in a uniform manner
  3. Clarity: Provide clear error messages and path resolution
  4. Navigation: Support intuitive directory navigation with memory of previous locations
  5. Validation: Ensure paths meet security and format requirements

Components

The system consists of three main components:

1. PathManager

PathManager is the core class responsible for all path-related operations. It handles:

  • Path normalization and expansion
  • Security boundary enforcement
  • Path validation for reading and writing
  • Directory change tracking
  • Path joining and relation checking
// Example: Creating and using PathManager
const pathManager = new PathManager(config);
pathManager.setProjectsBaseDir('/path/to/projects');
pathManager.setActiveProject('/path/to/projects/MyProject.xcodeproj');

// Normalize and validate paths
const normalizedPath = pathManager.normalizePath('~/projects/file.txt');
const isAllowed = pathManager.isPathAllowed(normalizedPath);

2. SafeFileOperations

SafeFileOperations builds on PathManager to provide secure file operations with consistent error handling. It includes:

  • Safe file reading with validation
  • Secure file writing with directory creation
  • Safe directory listing
  • Consistent error handling
// Example: Using SafeFileOperations
const fileOps = new SafeFileOperations(pathManager);

// Reading a file safely
const fileContent = await fileOps.readFile('config.json');

// Writing a file with proper validation
await fileOps.writeFile('settings.json', jsonContent, true);

Read the full file on GitHub · 205 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 205 lines · 1,477 tokens per session scan A 6580615b10ad

Subscribe to this mod's changes

path-management is a cursor rule published in the GitHub repository r-huijts/xcode-mcp-server (385 stars, last pushed 7mo ago), licensed MIT. It adds 1,477 tokens to every session, about $0.0074 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.