Skip to content

Tools should not be exeucted until all input guardrails have completed #624

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
samDobsonDev opened this issue Apr 29, 2025 · 2 comments
Closed
Labels
enhancement New feature or request

Comments

@samDobsonDev
Copy link

samDobsonDev commented Apr 29, 2025

What it says on the tin. Currently, tools that might take actions or impact an environment can be executed before all input guardrails have been completed. This might mean that a malicious prompt could call a tool with the intention of causing adverse effects before said prompt has been checked.

@samDobsonDev samDobsonDev added the enhancement New feature or request label Apr 29, 2025
@pakrym-oai
Copy link
Contributor

The guardrail is not considered a security boundary. There is always a chance that a user can craft a prompt that will pass thorough the guardrail.

You can run the guardrail agent explicitly before invoking the main agent to get the behavior that you are looking for.

@samDobsonDev
Copy link
Author

You can run the guardrail agent explicitly before invoking the main agent to get the behavior that you are looking for.

But then I lose inference concurrency between the agent's main run and its guardrails.

@samDobsonDev samDobsonDev closed this as not planned Won't fix, can't repro, duplicate, stale May 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants