Manage jobs. Actions: get, list, create, update, finalize, get-financial-summary, list-phases, get-phase, create-phase, update-phase, void-phase, get-phase-financial-summary. The wrapper preserves title/jobType on updates and compensates for Fergus read/write model mismatches. IMPORTANT: When cre...
AI agents use manage-jobs to create or update resources in Fergus MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fergus MCP Server environment.
The tool primarily performs reversible data modifications (create, update, void) on jobs and job phases within a job management platform. While it includes financial summary queries, these are read operations subordinate to the write capability. 'Finalize' and 'void-phase' indicate state transitions rather than irreversible deletion, placing this in Write rather than Destructive.
From the tool's definition Tool supports create, update, finalize, create-phase, update-phase, void-phase actions that modify job records. Actions like 'void-phase' suggest reversible state changes.
Attacks that exploit this kind of access
Manage jobs. Actions: get, list, create, update, finalize, get-financial-summary, list-phases, get-phase, create-phase, update-phase, void-phase, get-phase-financial-summary. The wrapper preserves title/jobType on updates and compensates for Fergus read/write model mismatches. IMPORTANT: When creating a job, always confirm jobType, customer, and site with the user before proceeding — do not infer or assume these from existing jobs or context. It is categorised as a Write tool in the Fergus MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fergus MCP Server MCP server in PolicyLayer and add a rule for manage-jobs: 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 Fergus MCP Server. Nothing to install.
manage-jobs 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 manage-jobs 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 manage-jobs. 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.
manage-jobs is provided by the Fergus MCP Server MCP server (jayco-design/fergus-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 →