jobhound_pause · JobHound MCP: Risk & Policy

WHAT IT DOES

What jobhound_pause does on JobHound

AI agents invoke jobhound_pause to trigger actions in JobHound. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why jobhound_pause needs a policy

This tool executes a control operation on the JobHound daemon, stopping its scan/apply loop. It doesn't read, write, or delete data, nor does it move money — it triggers an external system state change (process pause). Severity is low since pausing is reversible and the blast radius of misuse is minimal (jobs stop being applied to temporarily).

From the tool's definition 'Pause the JobHound daemon (scan loop stops applying)' — triggers an external operation that halts a running daemon process

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

jobhound_pause Rate-limited

jobhound_pause stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "jobhound_pause": {
      "limits": [
        {
          "counter": "jobhound_pause_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about jobhound_pause

What does the jobhound_pause tool do? +

Pause the JobHound daemon (scan loop stops applying). It is categorised as a Execute tool in the JobHound MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on jobhound_pause? +

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

What risk level is jobhound_pause? +

jobhound_pause is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit jobhound_pause? +

Yes. Add a rate_limit block to the jobhound_pause 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 jobhound_pause completely? +

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

jobhound_pause is provided by the JobHound MCP server (null-phnix/jobhound). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.