jobhound_scan · JobHound MCP: Risk & Policy

WHAT IT DOES

What jobhound_scan does on JobHound

AI agents invoke jobhound_scan 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_scan needs a policy

The server description indicates scanning involves querying external job APIs (Ashby, Greenhouse, Lever) to discover and score jobs, which constitutes triggering external operations. This goes beyond a simple local read — it actively reaches out to third-party systems.

From the tool's definition Tool name 'jobhound_scan' on a server described as enabling autonomous job search by 'scanning, scoring, and applying to jobs via APIs like Ashby, Greenhouse, and Lever'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

jobhound_scan Rate-limited

jobhound_scan 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_scan": {
      "limits": [
        {
          "counter": "jobhound_scan_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_scan

What does the jobhound_scan tool do? +

jobhound_scan. 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_scan? +

Register the JobHound MCP server in PolicyLayer and add a rule for jobhound_scan: 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_scan? +

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

Can I rate-limit jobhound_scan? +

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

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

jobhound_scan 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.