add_comments · Shell Executor MCP Server MCP: Risk & Policy

WHAT IT DOES

What add_comments does on Shell Executor MCP Server

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

WHY IT NEEDS A POLICY

Why add_comments needs a policy

The tool creates or modifies code content reversibly by inserting comments and documentation. While it operates within a server capable of command execution, add_comments itself is a Write operation (modifies code structure), not an Execute operation (which would require running external commands). The modification is reversible through standard version control or editing.

From the tool's definition Tool is named 'add_comments' and described as 'Add comprehensive comments and documentation to provided code'. This modifies code by injecting documentation, which is a reversible write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_comments Rate-limited

add_comments 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": {
    "add_comments": {
      "limits": [
        {
          "counter": "add_comments_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 Shell Executor MCP Server, so you can run agents against it safely.

FAQ

Questions about add_comments

What does the add_comments tool do? +

Add comprehensive comments and documentation to provided code. It is categorised as a Write tool in the Shell Executor 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 add_comments? +

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

What risk level is add_comments? +

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

Can I rate-limit add_comments? +

Yes. Add a rate_limit block to the add_comments 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 add_comments completely? +

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

add_comments is provided by the Shell Executor MCP Server MCP server (kosiew/zmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.