Low Risk

match_jobs

Get new job matches based on a saved job hunt configuration. Uses the filters saved in your job hunt (titles, locations, skills, salary, etc.) and only returns jobs you have not already seen, applied to, or rejected. To change filters, use update_job_hunt first.

Part of the JobGPT AutoApply MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call match_jobs to retrieve information from JobGPT AutoApply without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though match_jobs only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

xfigr-com-jobgpt.yaml
tools:
  match_jobs:
    rules:
      - action: allow

See the full JobGPT AutoApply policy for all 35 tools.

Tool Name match_jobs
Category Read
Risk Level Low

View all 35 tools →

Agents calling read-class tools like match_jobs have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the match_jobs tool do? +

Get new job matches based on a saved job hunt configuration. Uses the filters saved in your job hunt (titles, locations, skills, salary, etc.) and only returns jobs you have not already seen, applied to, or rejected. To change filters, use update_job_hunt first.. It is categorised as a Read tool in the JobGPT AutoApply MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on match_jobs? +

Add a rule in your Intercept YAML policy under the tools section for match_jobs. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the JobGPT AutoApply MCP server.

What risk level is match_jobs? +

match_jobs is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit match_jobs? +

Yes. Add a rate_limit block to the match_jobs rule in your Intercept 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 match_jobs completely? +

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

What MCP server provides match_jobs? +

match_jobs is provided by the JobGPT AutoApply MCP server (xfigr-com/jobgpt). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on JobGPT AutoApply

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.