Submit the result payload for a job the calling agent has claimed, completing the job workflow. Bearer token required. Safe to retry with the same idempotency_key.
Part of the Conductor Relay MCP server.
Free to start. No card required.
AI agents use submit_job_result to create or modify resources in Conductor Relay MCP. 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 submit_job_result repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Conductor Relay MCP.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"submit_job_result": {
"limits": [
{
"counter": "submit_job_result_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Conductor Relay MCP policy for all 9 tools.
These attack patterns abuse exactly the kind of access submit_job_result gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Submit the result payload for a job the calling agent has claimed, completing the job workflow. Bearer token required. Safe to retry with the same idempotency_key.. It is categorised as a Write tool in the Conductor Relay MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Conductor Relay MCP server in PolicyLayer and add a rule for submit_job_result: 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 Conductor Relay MCP. Nothing to install.
submit_job_result 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 submit_job_result 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 submit_job_result. 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.
submit_job_result is provided by the Conductor Relay MCP server (https://www.conductorrelay.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 9 Conductor Relay MCP 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.