# update_track_spec

Overwrite spec.md for an existing conductor track. Use to update technical decisions, architecture notes, or acceptance criteria.

Agent View of the PolicyLayer registry record for `update_track_spec`. HTML page: https://policylayer.com/tools/2loch-ness6-mempalace-mcp-dev/update-track-spec

## Facts

- Tool: `update_track_spec`
- Server: Mcp Dev (`2loch-ness6/mempalace-mcp-dev`) — https://policylayer.com/tools/2loch-ness6-mempalace-mcp-dev.md
- Homepage: https://github.com/2loch-ness6/mempalace-mcp-dev
- Risk category: Write (Medium risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "update_track_spec",
    "arguments": {}
  }
}
```

## Why update_track_spec is rated Medium

This tool creates or modifies data (spec.md content) reversibly within a project tracking system. It does not execute arbitrary code, delete data irreversibly, move money, or trigger external operations. The blast radius is limited to overwriting project documentation/specifications within a bounded codebase context tool.

From the tool's own definition: "Tool description states it will 'Overwrite spec.md for an existing conductor track' and is used to 'update technical decisions, architecture notes, or acceptance criteria.' The verb 'Overwrite' and the context of modifying a specification document indicate…"

## Use case

AI agents use update_track_spec to create or update resources in Mcp Dev, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Dev environment.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mcp Dev:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_track_spec": {
      "limits": [
        {
          "counter": "update_track_spec_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Mcp Dev (18)

- `run_tests` — Execute — https://policylayer.com/tools/2loch-ness6-mempalace-mcp-dev/run-tests.md
- `run_typecheck` — Execute — https://policylayer.com/tools/2loch-ness6-mempalace-mcp-dev/run-typecheck.md
- `get_all_changes` — Read — https://policylayer.com/tools/2loch-ness6-mempalace-mcp-dev/get-all-changes.md
- `get_branch_context` — Read — https://policylayer.com/tools/2loch-ness6-mempalace-mcp-dev/get-branch-context.md
- `get_changed_files` — Read — https://policylayer.com/tools/2loch-ness6-mempalace-mcp-dev/get-changed-files.md
- `get_file_ledger` — Read — https://policylayer.com/tools/2loch-ness6-mempalace-mcp-dev/get-file-ledger.md
- `get_git_diff` — Read — https://policylayer.com/tools/2loch-ness6-mempalace-mcp-dev/get-git-diff.md
- `get_session_changes` — Read — https://policylayer.com/tools/2loch-ness6-mempalace-mcp-dev/get-session-changes.md
- `get_track_index` — Read — https://policylayer.com/tools/2loch-ness6-mempalace-mcp-dev/get-track-index.md
- `get_track_plan` — Read — https://policylayer.com/tools/2loch-ness6-mempalace-mcp-dev/get-track-plan.md
- `get_track_spec` — Read — https://policylayer.com/tools/2loch-ness6-mempalace-mcp-dev/get-track-spec.md
- `list_tracks` — Read — https://policylayer.com/tools/2loch-ness6-mempalace-mcp-dev/list-tracks.md
- `search_code` — Read — https://policylayer.com/tools/2loch-ness6-mempalace-mcp-dev/search-code.md
- `create_track` — Write — https://policylayer.com/tools/2loch-ness6-mempalace-mcp-dev/create-track.md
- `log_change` — Write — https://policylayer.com/tools/2loch-ness6-mempalace-mcp-dev/log-change.md
- `mine_changed_files` — Write — https://policylayer.com/tools/2loch-ness6-mempalace-mcp-dev/mine-changed-files.md
- `update_track_index` — Write — https://policylayer.com/tools/2loch-ness6-mempalace-mcp-dev/update-track-index.md
- `update_track_plan` — Write — https://policylayer.com/tools/2loch-ness6-mempalace-mcp-dev/update-track-plan.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=2loch-ness6-mempalace-mcp-dev · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/2loch-ness6-mempalace-mcp-dev