microsoft / microsoft/agent-governance-toolkit
policy-engine: URL-sourced manifests may declare local bundle and data paths
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.3k
- Forks
- 1.1k
- Avg merge
- 5d 11h
- Merged PRs (30d)
- 142
Description
Upstream skips resolve_relative_paths for ManifestLocation::Url and does not reject filesystem-backed fields (bundle, data, data_paths) or an arbitrary query on URL-sourced manifests; SPECIFICATION.md 2.3 describes a rejection that is not implemented (noted as a caveat in #3940). Implement the rejection or amend the spec.
Found in the group review of the policy-engine retarget (#3939) and deferred from the follow-up (#3940).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read SPECIFICATION.md section 2.3, then trace the policy-engine handling of ManifestLocation::Url and resolve_relative_paths. Compare the current treatment of bundle, data, data_paths, and URL queries with the specification; done means either the filesystem-backed fields and arbitrary queries are rejected or the specification is amended to match the intended behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100