comment_issue
Comenta un issue o PR existente. ESCRIBE en GitHub.
This record as markdown: /tools/4bis-relay-showcase/comment-issue.md
What comment_issue does on 4bis Relay Showcase
AI agents use comment_issue to create or update resources in 4bis Relay Showcase, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 4bis Relay Showcase environment.
Why comment_issue is rated Medium
Creates or modifies data reversibly by posting comments to GitHub issues or pull requests.
From the tool's definition Comenta un issue o PR existente. ESCRIBE en GitHub.
Attacks that exploit this kind of access
The rule that runs comment_issue safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 4bis Relay Showcase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For comment_issue, this is the rule to start with:
comment_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.
The button opens the PolicyLayer dashboard: create your workspace, connect 4bis Relay Showcase, apply this rule, and every comment_issue call is checked against it from then on.
Questions about comment_issue
Comenta un issue o PR existente. ESCRIBE en GitHub. It is categorised as a Write tool in the 4bis Relay Showcase MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 4bis Relay Showcase MCP server in PolicyLayer and add a rule for comment_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 4bis Relay Showcase. Nothing to install.
comment_issue 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 comment_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.
Set action: deny in the PolicyLayer policy for comment_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.
comment_issue is provided by the 4bis Relay Showcase MCP server (FourBis/4bis.relay-showcase). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 4bis Relay Showcase, and thousands of servers like it.
This server
Across the catalogue