comment_on_issue · Tangled MCP Server MCP: Risk & Policy

WHAT IT DOES

What comment_on_issue does on Tangled MCP Server

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

WHY IT NEEDS A POLICY

Why comment_on_issue needs a policy

Adding a comment to an issue is a write operation that creates new data and modifies the issue record reversibly. It does not execute code, delete data, or move money. While comments are generally low-risk, in a collaborative platform context an AI agent could spam, harass, or post misleading information at scale, warranting medium severity. Confidence is high given the clear semantic meaning of 'comment'.

From the tool's definition Tool name is 'comment_on_issue' with description 'comment on an issue'. This creates new comment data on an existing issue, modifying the issue's state by adding content.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

comment_on_issue Rate-limited

comment_on_issue 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": {
    "comment_on_issue": {
      "limits": [
        {
          "counter": "comment_on_issue_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 Tangled MCP Server, so you can run agents against it safely.

FAQ

Questions about comment_on_issue

What does the comment_on_issue tool do? +

comment on an issue. It is categorised as a Write tool in the Tangled 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 comment_on_issue? +

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

What risk level is comment_on_issue? +

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

Can I rate-limit comment_on_issue? +

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

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

comment_on_issue is provided by the Tangled MCP Server MCP server (zzstoatzz/tangled-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.