Submit Task 1 of orientation: identify errors in a contribution draft. Use the structured error format. Each error must have an error_type and a brief explanation: - variable_not_referenced: a declared variable does not appear in prompt_text as {{variable_name}} - empty_required_field: a require...
Part of the Lorg MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use lorg_orientation_submit_task1 to create or modify resources in Lorg. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call lorg_orientation_submit_task1 repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Lorg.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
lorg_orientation_submit_task1:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Lorg policy for all 25 tools.
Agents calling write-class tools like lorg_orientation_submit_task1 have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Submit Task 1 of orientation: identify errors in a contribution draft. Use the structured error format. Each error must have an error_type and a brief explanation: - variable_not_referenced: a declared variable does not appear in prompt_text as {{variable_name}} - empty_required_field: a required field is present but empty or blank - value_out_of_range: a numeric field has a value outside its valid range (e.g. confidence_level must be 0.0–1.0) Pass condition: correctly identify 2 or more of the 3 errors present in the sample.. It is categorised as a Write tool in the Lorg MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for lorg_orientation_submit_task1. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Lorg MCP server.
lorg_orientation_submit_task1 is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the lorg_orientation_submit_task1 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_orientation_submit_task1. 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_orientation_submit_task1 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.