> For the complete documentation index, see [llms.txt](https://developer.collibra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.collibra.com/workflows/designing-workflows/processes/process-execution/restricting-groovy-script-io-access.md).

# Restricting Groovy script I/O access

You can request Collibra Support to restrict specific Java I/O and network methods in Groovy workflow scripts. Once applied, any script that calls a restricted method fails with an error. The restriction prevents workflows from accessing the local file system, making outbound network calls, or reading system environment variables, which reduces the risk of data exfiltration or unintended side effects.

## What can be restricted

The following Java classes and methods can be blocked on request:

* `java.nio.file.Files`
* `java.io.File`
* `java.net.URL`
* `java.net.HttpURLConnection`
* `java.net.Socket`
* `System.getenv()`
* `System.getProperties()`

## Impact on existing workflows

Before requesting the restriction, audit all Groovy script tasks in your workflows. Any script that calls a restricted method stops working after the restriction is applied.

## How to request

Contact [Collibra Support](https://support.collibra.com) to enable this restriction for your environment.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.collibra.com/workflows/designing-workflows/processes/process-execution/restricting-groovy-script-io-access.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.