Skip to content

Enforce effective MCP object allowlists - #117

Closed
lucarlig wants to merge 1 commit into
mainfrom
user/luca/enforce-effective-allowlists
Closed

Enforce effective MCP object allowlists#117
lucarlig wants to merge 1 commit into
mainfrom
user/luca/enforce-effective-allowlists

Conversation

@lucarlig

@lucarlig lucarlig commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Reject tool calls absent from the selected backend effective tool allowlist before plugins or backend connection.
  • Apply the same fail-closed check to prompts and resource URIs.
  • Add allowed_resource_uris to config/schema and document the new routing behavior.
  • Cover rejection-before-connection and old-config deserialization with regression tests.

Integration dependency

Draft until the ContextForge control-plane publisher populates allowed_resource_uris; it currently publishes resource display names only, so resource reads would otherwise fail closed.

Testing

  • cargo fmt --all --check
  • cargo clippy --locked --workspace --all-targets -- -D warnings
  • cargo nextest run --locked --workspace (211 passed)
  • cargo deny check advisories licenses
  • cargo build --locked --workspace
  • cargo shear --check-test-targets --deny-warnings --locked
  • mdbook build _context/wiki
  • mdbook test _context/wiki
  • git diff --check

Signed-off-by: lucarlig <luca.carlig@ibm.com>
@dawid-nowak

Copy link
Copy Markdown
Contributor

You might as well close this one. It is done as part of #114

@lucarlig

Copy link
Copy Markdown
Contributor Author

closed is part of #118

@lucarlig lucarlig closed this Aug 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants