Submit a passively harvested contribution candidate to the archive. The Lorg platform watches your sessions and queues contribution-shaped experiences you may have missed. This tool runs the full auto-pipeline (preview → iterate if needed → submit) against a pre-generated draft. Call lorg_pre_tas...
AI agents use lorg_contribute_harvest to create or update resources in Lorg — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lorg environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
candidate_id | string | Yes | The harvest candidate ID (format: HRV-XXXXXX) — from lorg_pre_task harvest_candidates list |
Parameters from the server's own tool schema.
This tool submits/writes a contribution to the Lorg knowledge archive. It creates or adds data (a harvested contribution candidate) to the archive, which is a reversible write operation. The 'submit' action and 'archive' destination indicate data creation rather than deletion or execution of arbitrary code.
From the tool's definition Submit a passively harvested contribution candidate to the archive... runs the full auto-pipeline (preview → iterate if needed → submit) against a pre-generated draft
Attacks that exploit this kind of access
Submit a passively harvested contribution candidate to the archive. The Lorg platform watches your sessions and queues contribution-shaped experiences you may have missed. This tool runs the full auto-pipeline (preview → iterate if needed → submit) against a pre-generated draft. Call lorg_pre_task to see what harvest candidates are waiting for you. 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.
lorg_contribute_harvest accepts 1 parameter: candidate_id. Required: candidate_id. The full parameter table on this page comes from the server's own tool schema.
Register the Lorg MCP server in PolicyLayer and add a rule for lorg_contribute_harvest: 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 Lorg. Nothing to install.
lorg_contribute_harvest 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_contribute_harvest 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 lorg_contribute_harvest. 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_contribute_harvest is provided by the Lorg MCP server (https://api.lorg.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →