init_project_commands · Instrument MCP Server MCP

WHAT IT DOES

What init_project_commands does on Instrument MCP Server

AI agents use init_project_commands to create or update resources in Instrument MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Instrument MCP Server environment.

WHY IT NEEDS A POLICY

Why init_project_commands needs a policy

This tool creates a directory and copies files into it, which is a reversible write operation. It initializes project structure by copying built-in YAML configuration files to a local project directory. No code execution, deletion, or financial action is involved. Severity is medium because it modifies the filesystem and could overwrite existing project configuration files.

From the tool's definition 初始化项目命令目录，复制内置 YAML 到当前项目的 .instrument_mcp/ — 'initializes project command directory, copies built-in YAML to current project'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

init_project_commands Rate-limited

init_project_commands 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "init_project_commands": {
      "limits": [
        {
          "counter": "init_project_commands_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Instrument MCP Server, so you can run agents against it safely.

FAQ

Questions about init_project_commands

What does the init_project_commands tool do? +

初始化项目命令目录，复制内置 YAML 到当前项目的 .instrument_mcp/。. It is categorised as a Write tool in the Instrument MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on init_project_commands? +

Register the Instrument MCP Server MCP server in PolicyLayer and add a rule for init_project_commands: 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 Instrument MCP Server. Nothing to install.

What risk level is init_project_commands? +

init_project_commands is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit init_project_commands? +

Yes. Add a rate_limit block to the init_project_commands 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.

How do I block init_project_commands completely? +

Set action: deny in the PolicyLayer policy for init_project_commands. 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.

What MCP server provides init_project_commands? +

init_project_commands is provided by the Instrument MCP Server MCP server (zeng-andrew/instrument-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.