Medium Risk

set_comment

Set a comment at a specified address (EOL, PRE, POST, or PLATE comment).

How to control set_comment ↓

What set_comment does on Kawaiidra MCP

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

Medium Risk

Why set_comment needs a policy

The tool creates or modifies reversible data (comments/annotations) within an analysis database. This is a Write operation rather than Read (it modifies state), Execute (it doesn't run external code), or Destructive (comments can be edited or deleted).

From the tool's definition Tool description states 'Set a comment at a specified address' — this modifies metadata within a Ghidra binary analysis project by adding or updating comments at specified locations.

Documented attack patterns abuse exactly the kind of access set_comment gives an agent:

How to control set_comment

PolicyLayer is an MCP gateway — it sits between your AI agents and Kawaiidra MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for set_comment:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_comment": {
      "limits": [
        {
          "counter": "set_comment_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Kawaiidra MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about set_comment

What does the set_comment tool do? +

Set a comment at a specified address (EOL, PRE, POST, or PLATE comment). It is categorised as a Write tool in the Kawaiidra MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_comment? +

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

What risk level is set_comment? +

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

Can I rate-limit set_comment? +

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

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

set_comment is provided by the Kawaiidra MCP server (wagonbomb/kawaiidra-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Kawaiidra MCP tool call.

Start from Kawaiidra MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

94 Kawaiidra MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.