jobs.remotive.search
Search curated remote-only job listings — filter by keywords and category (software-dev, design, marketing, data, devops, etc.). Returns title, company, salary, job type, location requirements, tags. Global remote positions only (Remotive)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/jobs.remotive.search.md
What jobs.remotive.search does on Apibase
AI agents call jobs.remotive.search to retrieve information from Apibase 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 |
|---|---|---|---|
limit | integer | — | Max results (1-50, default 20) |
search | string | — | Job search keywords (e.g. "python", "react developer", "product manager") |
category | string | — | Job category slug: software-dev, design, customer-support, writing, marketing, sales, product, business, data, devops, finance, hr, qa, all-others |
Parameters from the server's own tool schema.
Why jobs.remotive.search is rated Low
Tool retrieves job listing data without modifying systems or triggering external operations; pure information retrieval.
From the tool's definition Search curated remote-only job listings — filter by keywords and category. Returns title, company, salary, job type, location requirements, tags.
Attacks that exploit this kind of access
The rule that runs jobs.remotive.search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For jobs.remotive.search, this is the rule to start with:
jobs.remotive.search 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 Apibase, apply this rule, and every jobs.remotive.search call is checked against it from then on.
Questions about jobs.remotive.search
Search curated remote-only job listings — filter by keywords and category (software-dev, design, marketing, data, devops, etc.). Returns title, company, salary, job type, location requirements, tags. Global remote positions only (Remotive). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
jobs.remotive.search accepts 3 parameters: limit, search, category. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for jobs.remotive.search: 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 Apibase. Nothing to install.
jobs.remotive.search 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.remotive.search 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.remotive.search. 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.remotive.search is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue