Conversation
PR SummaryLow Risk Overview When generating from an OpenAPI spec, the scaffold also includes a Reviewed by Cursor Bugbot for commit 505c94e. Bugbot is set up for automated code reviews on this repo. Configure here. |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is ON, but it could not run because the branch was deleted or merged before autofix could start.
Reviewed by Cursor Bugbot for commit 505c94e. Configure here.
| lines.push( | ||
| "", | ||
| "policies:", | ||
| " - path: \"gate/policies/mcp_tool_allowlist.rego\"", |
There was a problem hiding this comment.
Policy path includes wrong directory prefix in connector YAML
Medium Severity
The policy path in the generated connector.yaml is gate/policies/mcp_tool_allowlist.rego, but connector.yaml itself lives inside the gate/ directory. The actual policy file is written to gate/policies/mcp_tool_allowlist.rego relative to the project root, which means relative to the config file it's just policies/mcp_tool_allowlist.rego. If Gate resolves this path relative to the config file's directory (a common convention), it would look for gate/gate/policies/mcp_tool_allowlist.rego, which doesn't exist. The generated README also instructs running from a Gate checkout, not the project root, so CWD-based resolution would also fail.
Reviewed by Cursor Bugbot for commit 505c94e. Configure here.


Summary
Testing