AI agents use gandi_comment_set to create or update resources in Gandi — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gandi environment.
The verb 'set' combined with 'comment' suggests creating or updating comments on Gandi resources (likely domains, certificates, or billing items based on sibling tools). This is reversible modification without destruction or financial impact, making it Write. Confidence is reduced from 0.75 to 0.60 due to empty description; however, the naming convention is clear enough to support Write classification.
From the tool's definition Tool name 'gandi_comment_set' indicates a write operation (set/modify), consistent with Write category tools that create or modify data reversibly. Description is empty, limiting certainty.
Attacks that exploit this kind of access
gandi_comment_set. It is categorised as a Write tool in the Gandi MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gandi MCP server in PolicyLayer and add a rule for gandi_comment_set: 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 Gandi. Nothing to install.
gandi_comment_set is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the gandi_comment_set 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.
Set action: deny in the PolicyLayer policy for gandi_comment_set. 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.
gandi_comment_set is provided by the Gandi MCP server (millsymills-com/gandi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →