jobs_rippling_board
List a company's Rippling job board. Lists a company's public Rippling board postings (thin listing — title, department, work location). The company is the Rippling board slug from its careers URL https://ats.rippling.com/{company}/jobs. Detail (full description, employment type) is fetched per j...
This record as markdown: /tools/crawlora-mcp/jobs-rippling-board.md
What jobs_rippling_board does on Crawlora
AI agents call jobs_rippling_board to retrieve information from Crawlora without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
remote | boolean | — | Filter by remote (true or false) |
company | string | Yes | Rippling board slug (careers URL) |
location | string | — | Filter: location contains |
department | string | — | Filter: department contains |
Parameters from the server's own tool schema.
Why jobs_rippling_board is rated Low
Even though jobs_rippling_board only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs jobs_rippling_board safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crawlora, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For jobs_rippling_board, this is the rule to start with:
jobs_rippling_board is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Crawlora, apply this rule, and every jobs_rippling_board call is checked against it from then on.
Questions about jobs_rippling_board
List a company's Rippling job board. Lists a company's public Rippling board postings (thin listing — title, department, work location). The company is the Rippling board slug from its careers URL https://ats.rippling.com/{company}/jobs. Detail (full description, employment type) is fetched per job via the single-job endpoint. Credential-free public ATS JSON. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
jobs_rippling_board accepts 4 parameters: remote, company, location, department. Required: company. The full parameter table on this page comes from the server's own tool schema.
Register the Crawlora MCP server in PolicyLayer and add a rule for jobs_rippling_board: 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 Crawlora. Nothing to install.
jobs_rippling_board is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the jobs_rippling_board 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.
Set action: deny in the PolicyLayer policy for jobs_rippling_board. 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.
jobs_rippling_board is provided by the Crawlora MCP server (crawlora-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crawlora, and thousands of servers like it.
This server
Across the catalogue