chore: fix permissions

[danielsinai]

User description

Description

What -

Why -

How -

Type of change

Please leave one option from the following and delete the rest:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• New Integration (non-breaking change which adds a new integration)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Non-breaking change (fix of existing functionality that will not change current behavior)
• Documentation (added/updated documentation)

All tests should be run against the port production environment(using a testing org).

Core testing checklist

• Integration able to create all default resources from scratch
• Resync finishes successfully
• Resync able to create entities
• Resync able to update entities
• Resync able to detect and delete entities
• Scheduled resync able to abort existing resync and start a new one
• Tested with at least 2 integrations from scratch
• Tested with Kafka and Polling event listeners
• Tested deletion of entities that don't pass the selector

Integration testing checklist

• Integration able to create all default resources from scratch
• Resync able to create entities
• Resync able to update entities
• Resync able to detect and delete entities
• Resync finishes successfully
• If new resource kind is added or updated in the integration, add example raw data, mapping and expected result to the examples folder in the integration directory.
• If resource kind is updated, run the integration with the example data and check if the expected result is achieved
• If new resource kind is added or updated, validate that live-events for that resource are working as expected
• Docs PR link here

Preflight checklist

• Handled rate limiting
• Handled pagination
• Implemented the code in async
• Support Multi account

Screenshots

Include screenshots from your environment showing how the resources of the integration will look.

API Documentation

Provide links to the API documentation used for this integration.

---

PR Type

Other

---

Description

• Remove WebFetch tool from allowed_tools in Claude workflow

---

Diagram Walkthrough

flowchart LR
  A["Claude Workflow"] -- "remove" --> B["WebFetch Tool"]

Loading

File Walkthrough

	Relevant files
Configuration changes	claude-generic.yml Remove WebFetch tool permission                                                    .github/workflows/claude-generic.yml Remove WebFetch from the allowed_tools list in the Claude workflow configuration +1/-1

---

[Copilot]

Pull Request Overview

This PR removes the WebFetch tool from the allowed tools list in the Claude GitHub workflow configuration, likely to address security concerns or reduce the scope of permissions for the AI assistant.

• Removes WebFetch tool from the allowed tools configuration
• Maintains other existing tools like Bash commands, Edit, GlobTool, GrepTool, and BatchTool

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Config Consistency Verify that any prompts or tasks relying on WebFetch are updated accordingly; removing it from allowed_tools may break existing automation steps or expectations in downstream workflows. allowed_tools: "Bash(git:*),Bash(gh:*),Bash(jq:*),Edit,GlobTool,GrepTool,BatchTool" system_prompt: |

[qodo-merge-pro]

PR Code Suggestions ✨

No code suggestions found for the PR.