Low Risk

job_finder

job_finder

How to control job_finder ↓

AI agents call job_finder to retrieve information from MCP Starter for Puch AI without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Based on the server's stated purpose of providing job searching tools and the naming convention 'job_finder', this tool most likely retrieves or queries job posting data without modifying it. However, confidence is reduced due to the empty tool description, which leaves some ambiguity about implementation details.

From the tool's definition Tool named 'job_finder' with empty description; server description indicates it provides 'fetch postings' and 'search opportunities' capabilities, which are read operations.

Documented attack patterns abuse exactly the kind of access job_finder gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Starter for Puch AI, and nothing reaches the server without passing your rules. This is the rule we recommend for job_finder:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "job_finder": {}
  }
}

job_finder is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register MCP Starter for Puch AI — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the job_finder tool do? +

job_finder. It is categorised as a Read tool in the MCP Starter for Puch AI MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on job_finder? +

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

What risk level is job_finder? +

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

Can I rate-limit job_finder? +

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

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

job_finder is provided by the MCP Starter for Puch AI MCP server (turboml-inc/mcp-starter). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Starter for Puch AI tool call.

Deterministic rules across all 12 MCP Starter for Puch AI tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

12 MCP Starter for Puch AI tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.