Submit an issue-level comment on a pull request.
AI agents use github_review_submit_comment to create or update resources in Promethean OS MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Promethean OS MCP environment.
This tool creates new content (a comment) on GitHub without permanently destroying data or executing arbitrary code. Comments are reversible—they can be edited, deleted, or otherwise managed by repository maintainers.
From the tool's definition Tool name and description explicitly indicate it 'Submit an issue-level comment on a pull request' — this creates new data (a comment) on GitHub in a reversible manner (comments can be edited or deleted).
Attacks that exploit this kind of access
Submit an issue-level comment on a pull request. It is categorised as a Write tool in the Promethean OS MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Promethean OS MCP server in PolicyLayer and add a rule for github_review_submit_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 Promethean OS MCP. Nothing to install.
github_review_submit_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 github_review_submit_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 github_review_submit_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.
github_review_submit_comment is provided by the Promethean OS MCP server (octave-commons/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 →