Creates a single job in a Workflow. Use workflow_id. Required: name + workflow_id. Supports custom fields as array of {code, value}.
AI agents use create_job to create or update resources in Rework MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rework MCP Server environment.
This tool creates new jobs within a workflow, which modifies system state by adding new records. This is a reversible Write operation—jobs can typically be deleted or archived without permanent data loss.
From the tool's definition Tool description states it 'Creates a single job in a Workflow' with required parameters 'name + workflow_id' and support for custom fields. The verb 'Creates' indicates data creation rather than retrieval.
Attacks that exploit this kind of access
Creates a single job in a Workflow. Use workflow_id. Required: name + workflow_id. Supports custom fields as array of {code, value}. It is categorised as a Write tool in the Rework MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Rework MCP Server MCP server in PolicyLayer and add a rule for create_job: 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 Rework MCP Server. Nothing to install.
create_job 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 create_job 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 create_job. 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.
create_job is provided by the Rework MCP Server MCP server (rework-com/rework-mcp-server). 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 →