Medium Risk

set_comments

Set comments at addresses (both disassembly and decompiler views)

How to control set_comments ↓

What set_comments does on Ida Domain

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

Medium Risk

Why set_comments needs a policy

This tool modifies IDA Pro's internal database by writing comment annotations to specific code addresses. While reversible (comments can be edited or deleted), it represents a Write action that alters the state of the reverse engineering database. Severity is medium because unauthorized comment injection could mislead analysis but does not delete data (Destructive) or execute arbitrary operations (Execute).

From the tool's definition Tool description states 'Set comments at addresses (both disassembly and decompiler views)' - the verb 'set' indicates modification of data. Comments are metadata annotations in the IDA Pro database that can be added, modified, or overwritten.

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

How to control set_comments

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

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

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

  1. Create a free account and register Ida Domain — 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_comments

What does the set_comments tool do? +

Set comments at addresses (both disassembly and decompiler views). It is categorised as a Write tool in the Ida Domain 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_comments? +

Register the Ida Domain MCP server in PolicyLayer and add a rule for set_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 Ida Domain. Nothing to install.

What risk level is set_comments? +

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

Can I rate-limit set_comments? +

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

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

set_comments is provided by the Ida Domain MCP server (xxyyue/ida_domain_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Ida Domain tool call.

Start from Ida Domain, 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.

74 Ida Domain 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.