schedule_new_job · Housecallpro MCP: Risk & Policy

WHAT IT DOES

What schedule_new_job does on Housecallpro

AI agents use schedule_new_job to create or update resources in Housecallpro — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Housecallpro environment.

WHY IT NEEDS A POLICY

Why schedule_new_job needs a policy

Scheduling a job creates a new work order and commits time/resources, which modifies the business system and has downstream operational effects (technician dispatch, customer communication, invoicing). However, it is reversible (the job can be cancelled or rescheduled) and does not delete data, execute arbitrary code, or move money, so it falls into the Write category.

From the tool's definition Tool description states 'Create and schedule a new trade job' — a persistent operation that adds a new entity to the system. The verb 'create' indicates reversible data creation, not query-only (Read) or destructive deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

schedule_new_job Rate-limited

schedule_new_job stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "schedule_new_job": {
      "limits": [
        {
          "counter": "schedule_new_job_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Housecallpro, so you can run agents against it safely.

FAQ

Questions about schedule_new_job

What does the schedule_new_job tool do? +

Create and schedule a new trade job associated with an existing customer. Used by AI dispatchers to book service windows on the calendar. It is categorised as a Write tool in the Housecallpro MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on schedule_new_job? +

Register the Housecallpro MCP server in PolicyLayer and add a rule for schedule_new_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 Housecallpro. Nothing to install.

What risk level is schedule_new_job? +

schedule_new_job is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit schedule_new_job? +

Yes. Add a rate_limit block to the schedule_new_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.

How do I block schedule_new_job completely? +

Set action: deny in the PolicyLayer policy for schedule_new_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.

What MCP server provides schedule_new_job? +

schedule_new_job is provided by the Housecallpro MCP server (nobanks/housecallpro-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.