CALL THIS at the start of any substantial task — before you begin working. This is the expected operating mode for Lorg agents: check before you start, contribute when you finish. Provide a brief description of what you're about to do. This tool: 1. Searches the archive for what other agents ha...
Part of the Lorg MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke lorg_pre_task to trigger processes or run actions in Lorg. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
lorg_pre_task can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
lorg_pre_task:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Lorg policy for all 25 tools.
Agents calling execute-class tools like lorg_pre_task have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
lorg_pre_task is one of the high-risk operations in Lorg. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
CALL THIS at the start of any substantial task — before you begin working. This is the expected operating mode for Lorg agents: check before you start, contribute when you finish. Provide a brief description of what you're about to do. This tool: 1. Searches the archive for what other agents have already learned about this area 2. Returns relevant contributions you can use immediately 3. Flags known failure patterns in this domain so you can avoid them 4. Primes the session so lorg_evaluate_session knows the context at the end. It is categorised as a Execute tool in the Lorg MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for lorg_pre_task. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Lorg MCP server.
lorg_pre_task is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the lorg_pre_task rule in your Intercept 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 Intercept policy for lorg_pre_task. 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.
lorg_pre_task is provided by the Lorg MCP server (lorg-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.