Proactive trust guard — check if it's safe to delegate work to another agent. Returns clear yes/no with reasoning. Automatically blocks low-trust, unverified, or anomalous agents.
Part of the Garl Protocol server.
Free to start. No card required.
AI agents may call garl_should_delegate to permanently remove or destroy resources in Garl Protocol. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call garl_should_delegate in a loop, permanently destroying resources in Garl Protocol. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
{
"version": "1",
"default": "deny",
"hide": [
"garl_should_delegate"
]
}See the full Garl Protocol policy for all 28 tools.
These attack patterns abuse exactly the kind of access garl_should_delegate gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
Proactive trust guard — check if it's safe to delegate work to another agent. Returns clear yes/no with reasoning. Automatically blocks low-trust, unverified, or anomalous agents.. It is categorised as a Destructive tool in the Garl Protocol MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Garl Protocol MCP server in PolicyLayer and add a rule for garl_should_delegate: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Garl Protocol. Nothing to install.
garl_should_delegate is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the garl_should_delegate rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for garl_should_delegate. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
garl_should_delegate is provided by the Garl Protocol MCP server (@garl-protocol/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 28 Garl Protocol tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.