{"version":"2.1.251","anchor":"workflow-scripts-outside-readable-paths-are-now-denied","canonical_anchor":"workflow-scripts-outside-readable-paths-are-now-denied","heading":"Workflow scripts outside readable paths are now denied","tier":"notice","area":"Workflows","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/workflow-scripts-outside-readable-paths-are-now-denied","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Workflow scripts outside readable paths are now denied\n\nA workflow whose script sits outside your readable paths is now denied outright.\n\n**What**\n\nIf a workflow's script file sits outside the set of paths the session is allowed to read, the tool now denies the call outright instead of quietly carrying on.\n\n**Details**\n\n- The denial happens in the workflow tool's permission check, so it is reported as a permission failure rather than a missing file.\n\n**Evidence**\n\n`workflow scriptPath outside the readable set`\n\n- Area: Workflows\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}