AI agents use add_issue_comment to create or update resources in MCP-Brave-Search — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP-Brave-Search environment.
This tool creates new content (a comment) that is reversible (can typically be edited or deleted). It modifies state by appending data to an issue but does not irreversibly destroy data. The severity is medium because misuse could spam issues, add misleading information, or disrupt project collaboration, but the blast radius is contained to a single issue's comments and the action is reversible.
From the tool's definition Tool name 'add_issue_comment' and description 'Add a comment to an existing issue' indicate creation of new comment data on an existing issue.
Documented attack patterns abuse exactly the kind of access add_issue_comment gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-Brave-Search, and nothing reaches the server without passing your rules. This is the rule we recommend for add_issue_comment:
{
"version": "1",
"default": "deny",
"tools": {
"add_issue_comment": {
"limits": [
{
"counter": "add_issue_comment_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_issue_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.
Free to start. No card required.
Add a comment to an existing issue. It is categorised as a Write tool in the MCP-Brave-Search MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP-Brave-Search MCP server in PolicyLayer and add a rule for add_issue_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 MCP-Brave-Search. Nothing to install.
add_issue_comment 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 add_issue_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.
Set action: deny in the PolicyLayer policy for add_issue_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.
add_issue_comment is provided by the MCP-Brave-Search MCP server (modelcontextprotocol/servers-archived). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP-Brave-Search, 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.
59 MCP-Brave-Search tools catalogued and risk-classified — across an index of 43,000+ MCP servers.